update_project · Omniplan MCP: Risk & Policy

WHAT IT DOES

What update_project does on Omniplan

AI agents use update_project 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 update_project needs a policy

The tool modifies project metadata reversibly based on its name and the server's stated capability to enable 'manipulation of... project metadata.' This is a Write operation (creates or modifies data reversibly) rather than Read (would be get_project_info), Destructive (no irreversible deletion), Execute (no arbitrary code execution), or Financial.

From the tool's definition Tool name 'update_project' combined with server description indicating 'creation and manipulation of... project metadata' suggests modifying project-level data. No destructive language (delete, drop, purge) and no financial operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_project Rate-limited

update_project 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": {
    "update_project": {
      "limits": [
        {
          "counter": "update_project_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 update_project

What does the update_project tool do? +

update_project. 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 update_project? +

Register the Omniplan MCP server in PolicyLayer and add a rule for update_project: 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 update_project? +

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

Can I rate-limit update_project? +

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

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

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