Comet (Perplexity)
What Comet’s own help pages, docs and terms said on 1 October 2026, by the same six questions we ask of every agent. We didn’t test it for this page. “Not documented” means we didn’t find it on the vendor’s pages; it doesn’t mean the feature is missing.
Browser agent
- Can you limit it?
- Block sites; admin read-only
- Does it ask first?
- Pauses for sensitive acts
- Can you stop it?
- Pause or block
- Is there a record someone outside can check?
- Not documented
- What about sub-agents?
- Not documented
- Can you test it yourself?
- Not documented for MCP
What the vendor’s pages say
You can block Comet on chosen sites, and enterprise admins can set a domain to Read Only or No Access. Admins can also turn on "Always Allow", which lets it act "without having to confirm" (permissions). Otherwise, for actions like sending an email, Comet "pauses for your confirmation regardless of whether our systems detect suspicious activity" (prompt injection). You can "pause Assistant's access or block specific sites anytime" (controls). Enterprise audit logs, for 50 or more seats, go to the organisation's own webhook (audit logs).
Every statement above was checked on the vendor’s own page on 1 October 2026; each links to its source.
Run this test on yours
Delegus Check gives your agent a permission and a one-hour test server, then shows every action it tries and what was refused. It works today with agents that accept a custom MCP server, including Claude on any plan.
Corrections
Vendors and readers: if anything here is out of date, write to hello@delegus.ai and we’ll fix it. Each change is listed here with its date.
- 1 October 2026: first published. All vendor statements checked that day.