AI agents call export_history to retrieve information from Django MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'export_history' implies reading/retrieving historical data (e.g., shell command history or session logs). With no description available, confidence is low. Classified as Read since export typically means retrieving data, but could potentially expose sensitive session data hence medium severity. The sibling 'clear_history' tool suggests this is about session/command history in the Django shell environment.
From the tool's definition Tool name 'export_history' and empty description; server context mentions 'clear_history' sibling tool suggesting a history/session log feature
Documented attack patterns abuse exactly the kind of access export_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 export_history:
{
"version": "1",
"default": "deny",
"tools": {
"export_history": {}
}
}export_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
export_history. It is categorised as a Read tool in the Django MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Django MCP Server MCP server in PolicyLayer and add a rule for export_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.
export_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the export_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 export_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.
export_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.