AI agents call delete_study to permanently remove resources in Document Loader MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'delete_study' tool performs deletion of a study entity, which is an irreversible action that cannot be undone. Even though the description is empty, the explicit 'delete' verb in the tool name clearly indicates destructive capability. This falls into the Destructive category rather than Execute because deletion is the primary outcome, not a side effect of parameterized execution.
From the tool's definition Tool name 'delete_study' combined with context of document/data management server indicates irreversible deletion operation. Description is empty, limiting confidence but the verb 'delete' is definitive for destructive action.
Documented attack patterns abuse exactly the kind of access delete_study gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Document Loader MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_study:
{
"version": "1",
"default": "deny",
"hide": [
"delete_study"
]
}delete_study disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
delete_study. It is categorised as a Destructive tool in the Document Loader MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Document Loader MCP Server MCP server in PolicyLayer and add a rule for delete_study: 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 Document Loader MCP Server. Nothing to install.
delete_study is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_study 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.
Set action: deny in the PolicyLayer policy for delete_study. 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.
delete_study is provided by the Document Loader MCP Server MCP server (awslabs.document-loader-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Document Loader MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 Document Loader MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.