Add a task to a work order. ALWAYS confirm with user before calling.
AI agents use add-work-order-task to create or update resources in Cpp Espace — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cpp Espace environment.
This tool creates or modifies data (adding a task to a work order) but does not irreversibly delete data, move money, or execute arbitrary code. It is reversible via delete operations available on this server (delete-work-order). The moderate severity reflects that adding incorrect tasks could disrupt facility operations, but the impact is bounded to a single work order and can be corrected.
From the tool's definition Tool description states 'Add a task to a work order', which creates new data (task) and modifies an existing work order reversibly.
Attacks that exploit this kind of access
Add a task to a work order. ALWAYS confirm with user before calling. It is categorised as a Write tool in the Cpp Espace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cpp Espace MCP server in PolicyLayer and add a rule for add-work-order-task: 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 Cpp Espace. Nothing to install.
add-work-order-task 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 add-work-order-task 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 add-work-order-task. 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.
add-work-order-task is provided by the Cpp Espace MCP server (norm613/cpp-espace-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 →