AI agents use assign_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.
Based on naming convention and server context, 'assign_resource' most likely creates or modifies resource assignments within a project (reversible operation). This is a Write action—it changes project state but does not irreversibly delete data or execute arbitrary code. Severity is medium because misuse could disrupt project planning and resource allocation, but changes can typically be undone.
From the tool's definition Tool name 'assign_resource' in an OmniPlan project management context. No description provided. Context sibling tools include create_resource, delete_resource, create_task, add_dependency, suggesting CRUD operations on project entities.
Attacks that exploit this kind of access
assign_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.
Register the Omniplan MCP server in PolicyLayer and add a rule for assign_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.
assign_resource is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the assign_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.
Set action: deny in the PolicyLayer policy for assign_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.
assign_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.
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 →