delete_scout

THE RISK

Critical Risk

Why delete_scout needs a policy

This tool irreversibly removes data (a scout and its associated data) with no recovery mechanism. This is a core Destructive category action. Severity is high because deletion of monitoring/research tasks could disrupt ongoing operations or cause loss of important research data, though the blast radius is limited to individual scout records rather than system-wide impact (which would be critical).

From the tool's definition Tool description explicitly states 'Permanently delete a scout and all its data. This action cannot be undone.' The words 'Permanently delete' and 'cannot be undone' are definitional markers of irreversible data destruction.

Documented attack patterns abuse exactly the kind of access delete_scout gives an agent:

POLICY

How to control delete_scout

PolicyLayer is an MCP gateway — it sits between your AI agents and Yutori MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_scout:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_scout"
  ]
}

delete_scout disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Yutori MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Yutori MCP tools

Execute run_browsing_task Execute a one-time web browsing task. The navigator agent runs a browser and Execute run_research_task Execute a one-time deep web research task. The research agent searches, Write create_scout Create a monitoring scout for continuous web monitoring. Scouts track changes relevant to Write edit_scout Update an existing scout Read get_browsing_task_result Poll for browsing task status and result. Call until status is Read get_research_task_result Poll for research task status and result. Call until status is Read get_scout_detail Get detailed information about a specific scout. Read get_scout_updates Get paginated updates/reports for a scout. Each update contains findings from a run.

All 11 Yutori MCP tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Yutori MCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_scout

What does the delete_scout tool do? +

Permanently delete a scout and all its data. This action cannot be undone. It is categorised as a Destructive tool in the Yutori MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_scout? +

Register the Yutori MCP server in PolicyLayer and add a rule for delete_scout: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Yutori MCP. Nothing to install.

What risk level is delete_scout? +

delete_scout is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_scout? +

Yes. Add a rate_limit block to the delete_scout rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block delete_scout completely? +

Set action: deny in the PolicyLayer policy for delete_scout. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides delete_scout? +

delete_scout is provided by the Yutori MCP server (yutori-ai/yutori-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Yutori MCP tool call.

Start from Yutori MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →