delete_instruction

THE RISK

Critical Risk

Why delete_instruction needs a policy

This tool permanently removes instruction files, which cannot be undone. Deletion is an irreversible operation that destroys data. While the blast radius is somewhat contained to instruction files rather than critical system data, unauthorized or accidental deletion of instructions could disrupt workflows, remove important prompt configurations, or require manual restoration.

From the tool's definition Tool name is 'delete_instruction' and description states it will 'Delete a VS Code .instructions.md file from the prompts directory.' The verb 'Delete' combined with file removal indicates irreversible data destruction.

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

POLICY

How to control delete_instruction

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

policy.json

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

delete_instruction 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 Mode Manager 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 Mode Manager MCP tools

Write configure_memory_optimization Configure memory optimization settings for auto-optimization behavior. Write create_instruction Create a new VS Code .instructions.md file with the specified description and content. Write optimize_memory Manually optimize a memory file using AI to reorganize and consolidate entries while prese Write remember remember Write update_instruction Update an existing VS Code .instructions.md file with new description or content. Read get_instruction Get the raw content of a VS Code .instructions.md file. Read list_instructions List all VS Code .instructions.md files in the prompts directory. Read memory_stats Get detailed statistics and optimization status for a memory file.

All 9 Mode Manager 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 Mode Manager 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_instruction

What does the delete_instruction tool do? +

Delete a VS Code .instructions.md file from the prompts directory. It is categorised as a Destructive tool in the Mode Manager 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_instruction? +

Register the Mode Manager MCP server in PolicyLayer and add a rule for delete_instruction: 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 Mode Manager MCP. Nothing to install.

What risk level is delete_instruction? +

delete_instruction 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_instruction? +

Yes. Add a rate_limit block to the delete_instruction 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_instruction completely? +

Set action: deny in the PolicyLayer policy for delete_instruction. 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_instruction? +

delete_instruction is provided by the Mode Manager MCP server (niclasolofsson/mode-manager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mode Manager MCP tool call.

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

CHECK YOUR STACK →