get_document_history
AI agents call get_document_history to retrieve information from Mnemosyne MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix is characteristic of read operations that query and retrieve data without side effects. While the empty description limits confidence, the tool name and its position among other CRUD operations (create_*, delete, check_*) strongly suggests it performs a retrieval operation. No evidence of modification, deletion, or execution.
From the tool's definition Tool name 'get_document_history' indicates retrieval of historical data without modification. The description is empty, but the naming convention (get_*) and context within a knowledge graph management system (alongside query, create, and manage operations)…
Attacks that exploit this kind of access
get_document_history. It is categorised as a Read tool in the Mnemosyne MCP MCP Server, which means it retrieves data without modifying state.
Register the Mnemosyne MCP server in PolicyLayer and add a rule for get_document_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 Mnemosyne MCP. Nothing to install.
get_document_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 get_document_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 get_document_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.
get_document_history is provided by the Mnemosyne MCP server (sophia-labs/mnemosyne-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 →