Export a Cursor AI chat session to Markdown or JSON format. Returns the formatted content.
Part of the Cursor History server.
Free to start. No card required.
AI agents use cursor_history_export to create or modify resources in Cursor History. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call cursor_history_export repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Cursor History.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"cursor_history_export": {
"limits": [
{
"counter": "cursor_history_export_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Cursor History policy for all 8 tools.
These attack patterns abuse exactly the kind of access cursor_history_export gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Export a Cursor AI chat session to Markdown or JSON format. Returns the formatted content.. It is categorised as a Write tool in the Cursor History MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cursor History MCP server in PolicyLayer and add a rule for cursor_history_export: 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 Cursor History. Nothing to install.
cursor_history_export is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the cursor_history_export 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 cursor_history_export. 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.
cursor_history_export is provided by the Cursor History MCP server (cursor-history-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Cursor History tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.