Critical Risk →

frappe_delete_document

Delete a Frappe document

Part of the Frappe Dev MCP Server server.

frappe_delete_document can permanently delete data in Frappe Dev MCP Server, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE FRAPPE DEV MCP SERVER →

Free to start. No card required.

AI agents may call frappe_delete_document to permanently remove or destroy resources in Frappe Dev MCP Server. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call frappe_delete_document in a loop, permanently destroying resources in Frappe Dev MCP Server. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "frappe_delete_document"
  ]
}

See the full Frappe Dev MCP Server policy for all 29 tools.

Get this rule live on your own Frappe Dev MCP Server server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY FRAPPE DEV MCP SERVER →

View all 29 tools →

These attack patterns abuse exactly the kind of access frappe_delete_document gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so frappe_delete_document only ever does what you allow.

SECURE FRAPPE DEV MCP SERVER →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the frappe_delete_document tool do? +

Delete a Frappe document. It is categorised as a Destructive tool in the Frappe Dev MCP Server 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 frappe_delete_document? +

Register the Frappe Dev MCP Server MCP server in PolicyLayer and add a rule for frappe_delete_document: 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 Frappe Dev MCP Server. Nothing to install.

What risk level is frappe_delete_document? +

frappe_delete_document 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 frappe_delete_document? +

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

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

frappe_delete_document is provided by the Frappe Dev MCP Server MCP server (frappe-dev-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Frappe Dev MCP Server tool call.

Deterministic rules across all 29 Frappe Dev MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.