AI agents call clear_history to permanently remove resources in Django MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name 'clear_history' suggests purging/deleting historical records, which is typically irreversible. Given the server context mentions a 'stateful Django shell environment' and sibling tool 'export_history', this likely clears execution/session history. The empty description lowers confidence, but 'clear' operations are canonically destructive.
From the tool's definition Tool name 'clear_history' with empty description. The name strongly implies irreversible deletion of history data.
Documented attack patterns abuse exactly the kind of access clear_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Django MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for clear_history:
{
"version": "1",
"default": "deny",
"hide": [
"clear_history"
]
}clear_history 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.
clear_history. It is categorised as a Destructive tool in the Django MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Django MCP Server MCP server in PolicyLayer and add a rule for clear_history: 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 Django MCP Server. Nothing to install.
clear_history 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 clear_history 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 clear_history. 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.
clear_history is provided by the Django MCP Server MCP server (joshuadavidthomas/mcp-django). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Django 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.
13 Django MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.