Retrieve a previously indexed file from the Filing Cabinet.
AI agents call get_from_cabinet to retrieve information from Mnehmos Synch without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple read operation—fetching stored data from an existing index. There is no creation, modification, deletion, or execution of external operations. The retrieval of indexed files is a foundational read capability with minimal security risk unless the retrieved data itself is sensitive, but that is a data classification issue rather than a tool capability issue.
From the tool's definition Tool retrieves a previously indexed file from the Filing Cabinet. The name 'get_from_cabinet' and description 'Retrieve a previously indexed file' clearly indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Retrieve a previously indexed file from the Filing Cabinet. It is categorised as a Read tool in the Mnehmos Synch MCP Server, which means it retrieves data without modifying state.
Register the Mnehmos Synch MCP server in PolicyLayer and add a rule for get_from_cabinet: 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 Mnehmos Synch. Nothing to install.
get_from_cabinet 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_from_cabinet 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_from_cabinet. 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_from_cabinet is provided by the Mnehmos Synch MCP server (mnehmos/mnehmos.synch.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 →