move_resource · Omniplan MCP: Risk & Policy

WHAT IT DOES

What move_resource does on Omniplan

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

The tool appears to create or modify resource state (moving/reassigning) within a project management context, making it a Write operation. It is reversible (resources can be moved again), so not Destructive. Severity is medium because misuse could disrupt project structure, but the impact is limited to resource allocation without financial consequences.

From the tool's definition Tool name 'move_resource' suggests relocating or reassigning a resource within OmniPlan 4. Given the sibling tools include 'assign_resource' and 'create_resource', this likely modifies resource allocation or positioning rather than deleting it.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_resource Rate-limited

move_resource 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": {
    "move_resource": {
      "limits": [
        {
          "counter": "move_resource_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 move_resource

What does the move_resource tool do? +

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

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

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

Can I rate-limit move_resource? +

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

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

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