delete_agent_conversation
Delete a conversation session with an agent. This cannot be undone.
This record as markdown: /tools/namastexlabs-automagik-tools/delete-agent-conversation.md
What delete_agent_conversation does on Automagik Tools
AI agents call delete_agent_conversation to permanently remove resources in Automagik Tools, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_agent_conversation is rated Critical
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.
Attacks that exploit this kind of access
The rule that runs delete_agent_conversation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Automagik Tools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_agent_conversation, this is the rule to start with:
delete_agent_conversation is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Automagik Tools, apply this rule, and every delete_agent_conversation call is checked against it from then on.
Questions about delete_agent_conversation
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.
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.
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.
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.
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.
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.
More on Automagik Tools, and thousands of servers like it.
Across the catalogue