file_to_cabinet · Mnehmos Synch MCP: Risk & Policy

WHAT IT DOES

What file_to_cabinet does on Mnehmos Synch

AI agents use file_to_cabinet to create or update resources in Mnehmos Synch — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mnehmos Synch environment.

WHY IT NEEDS A POLICY

Why file_to_cabinet needs a policy

This tool creates a new index entry in the Filing Cabinet system, storing a file reference along with a summary and metadata. This is a reversible write operation — it adds structured data to a persistent store without deleting or overwriting anything. The blast radius is medium because an AI agent could index incorrect summaries or metadata, polluting the retrieval system used across sessions and agents.

From the tool's definition 'Index a file into the Filing Cabinet for fast future retrieval. Provide a summary and key metadata.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

file_to_cabinet Rate-limited

file_to_cabinet stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "file_to_cabinet": {
      "limits": [
        {
          "counter": "file_to_cabinet_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mnehmos Synch, so you can run agents against it safely.

FAQ

Questions about file_to_cabinet

What does the file_to_cabinet tool do? +

Index a file into the Filing Cabinet for fast future retrieval. Provide a summary and key metadata. It is categorised as a Write tool in the Mnehmos Synch MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on file_to_cabinet? +

Register the Mnehmos Synch MCP server in PolicyLayer and add a rule for file_to_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.

What risk level is file_to_cabinet? +

file_to_cabinet is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit file_to_cabinet? +

Yes. Add a rate_limit block to the file_to_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.

How do I block file_to_cabinet completely? +

Set action: deny in the PolicyLayer policy for file_to_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.

What MCP server provides file_to_cabinet? +

file_to_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.