delete_agent_conversation

THE RISK

Critical Risk

Why delete_agent_conversation needs a policy

This tool irreversibly deletes conversation data. While the blast radius is limited to conversation history (not financial or system-critical data), the irreversible nature and explicit 'cannot be undone' warning place this firmly in the Destructive category. Severity is high because an agent that misuses this could permanently erase user interaction history, losing context and evidence.

From the tool's definition Tool description explicitly states 'Delete a conversation session with an agent. This cannot be undone.' The words 'Delete' and 'cannot be undone' are direct indicators of irreversible data destruction.

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

POLICY

How to control delete_agent_conversation

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

policy.json

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

delete_agent_conversation 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 Automagik Tools — 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 Automagik Tools tools

Destructive delete_credential Delete a stored credential. Destructive delete_message Delete message for everyone. Only works for messages from you (from_me=True), within ~48 h Destructive delete_schedule Delete a schedule. Destructive delete_source Delete a workflow source. Destructive delete_task Delete a task execution. Destructive delete_team_collaboration Delete a team collaboration session. This cannot be undone. Destructive delete_workflow Delete a synchronized workflow. Destructive delete_workflow_execution Delete a workflow execution session. This cannot be undone.

All 122 Automagik Tools 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 Automagik Tools → 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_agent_conversation

What does the delete_agent_conversation tool do? +

Delete a conversation session with an agent. This cannot be undone. It is categorised as a Destructive tool in the Automagik Tools 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_agent_conversation? +

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

What risk level is delete_agent_conversation? +

delete_agent_conversation 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_agent_conversation? +

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

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

delete_agent_conversation is provided by the Automagik Tools MCP server (namastexlabs/automagik-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Automagik Tools tool call.

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

CHECK YOUR STACK →