Get the revision history of a document. See who changed what and when.
AI agents call sanity_history to retrieve information from Sanity MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves document revision history and change metadata—a purely informational query with no side effects. It does not create, modify, delete, execute code, or commit financial actions. The most severe sibling operations are destructive (sanity_delete) and write operations (sanity_create), but this tool only reads historical audit data, placing it firmly in the Read category with low severity.
From the tool's definition Tool description states 'Get the revision history of a document' which retrieves audit/version data without modification. The phrase 'See who changed what and when' confirms it is a read-only query operation that accesses historical metadata.
Attacks that exploit this kind of access
Get the revision history of a document. See who changed what and when. It is categorised as a Read tool in the Sanity MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sanity MCP Server MCP server in PolicyLayer and add a rule for sanity_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 Sanity MCP Server. Nothing to install.
sanity_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 sanity_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 sanity_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.
sanity_history is provided by the Sanity MCP Server MCP server (purple-horizons/sanity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →