Meta Muse
What Meta Muse’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.
Assistant
- Can you limit it?
- Two levels; per site
- Does it ask first?
- Allow once to Always allow
- Can you stop it?
- Stop the task
- Is there a record someone outside can check?
- Not documented
- What about sub-agents?
- A separate approving agent
- Can you test it yourself?
- Muse Code: MCP and headless runs
What the vendor’s pages say
Connectors can be set to "Ask for some actions" or "Always ask". When it asks, you can allow once, for the task, for the site, or "Always allow", which applies to that connector "in the future without asking again". An activity log keeps "a chronological record of actions", and Meta notes that some actions, "like sending an email, cannot be reversed" (approvals). Facebook, Instagram and Threads "are connected automatically" when they share an Accounts Center, and "Meta doesn't review custom connectors" (connectors). A separate agent, the Sentinel, sits in front of the internet: "Nothing Muse does reaches the internet unless the Sentinel approves it". Muse Code accepts MCP servers and has an approval mode, "never", in which "nothing stops for approval".
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.