Critical Risk →

delete-doc

delete-doc

How to control delete-doc ↓

AI agents call delete-doc to permanently remove resources in MCP-Google-Doc — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Deletion of documents is an irreversible action that cannot be undone. This falls under the Destructive category (most severe applicable category). Severity is high because unauthorized deletion could result in permanent loss of user data and significant business/personal impact.

From the tool's definition Tool name 'delete-doc' combined with server description stating the MCP server enables 'deleting documents'. The tool performs irreversible deletion of Google Docs.

Documented attack patterns abuse exactly the kind of access delete-doc gives an agent:

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-doc"
  ]
}

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

  1. Create a free account and register MCP-Google-Doc — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the delete-doc tool do? +

delete-doc. It is categorised as a Destructive tool in the MCP-Google-Doc 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-doc? +

Register the MCP-Google-Doc MCP server in PolicyLayer and add a rule for delete-doc: 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 MCP-Google-Doc. Nothing to install.

What risk level is delete-doc? +

delete-doc 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-doc? +

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

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

delete-doc is provided by the MCP-Google-Doc MCP server (ophydami/mcp-google-doc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP-Google-Doc tool call.

Deterministic rules across all 8 MCP-Google-Doc tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

8 MCP-Google-Doc tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.