save_document · Omniplan MCP: Risk & Policy

WHAT IT DOES

What save_document does on Omniplan

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

WHY IT NEEDS A POLICY

Why save_document needs a policy

The 'save_document' operation creates or modifies project files/state by persisting changes (reversible write operation). Without a description, we cannot determine if it saves to external files (which could be destructive if overwriting) or merely flushes in-memory project state. In the context of OmniPlan 4, this likely saves project metadata and task structure.

From the tool's definition Tool name 'save_document' indicates a write operation that persists data. Server context shows OmniPlan 4 project management with create/modify/delete operations on tasks and resources. Empty description limits confidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_document Rate-limited

save_document 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": {
    "save_document": {
      "limits": [
        {
          "counter": "save_document_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 Omniplan, so you can run agents against it safely.

FAQ

Questions about save_document

What does the save_document tool do? +

save_document. It is categorised as a Write tool in the Omniplan MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on save_document? +

Register the Omniplan MCP server in PolicyLayer and add a rule for save_document: 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 Omniplan. Nothing to install.

What risk level is save_document? +

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

Can I rate-limit save_document? +

Yes. Add a rate_limit block to the save_document 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 save_document completely? +

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

save_document is provided by the Omniplan MCP server (johntrandall/omniplan-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.