Permanently deletes a study and all associated data. Releases unused reserved credits.
AI agents call delete_study to permanently remove resources in Mcp Usercall — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes data (studies and associated interview data). While the blast radius is somewhat limited to a single study rather than system-wide, the permanent loss of research data, user responses, and insights represents a high-severity destructive action. An AI agent misusing this could destroy valuable research datasets and user interview records that cannot be recovered.
From the tool's definition Tool description states 'Permanently deletes a study and all associated data' — the word 'Permanently' and 'deletes' are explicit indicators of irreversible destruction.
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 Mcp Usercall, 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.
Permanently deletes a study and all associated data. Releases unused reserved credits. It is categorised as a Destructive tool in the Mcp Usercall MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Usercall 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 Mcp Usercall. 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 Mcp Usercall MCP server (junetic/usercall-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Usercall, 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.
5 Mcp Usercall tools catalogued and risk-classified — across an index of 43,000+ MCP servers.