Update fields on an existing work order. Requires technician role.
AI agents use update_workorder to create or update resources in Maximo Enterprise MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Maximo Enterprise MCP environment.
This tool creates or modifies data (work order fields) in a reversible manner, fitting the Write category. Severity is medium because work order updates in Maximo can affect operational workflows, maintenance scheduling, and asset tracking, but the changes are non-destructive and can be corrected. The role requirement (technician) provides some access control mitigation.
From the tool's definition Tool description states 'Update fields on an existing work order', which modifies data reversibly without deletion or destruction.
Attacks that exploit this kind of access
Update fields on an existing work order. Requires technician role. It is categorised as a Write tool in the Maximo Enterprise MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Maximo Enterprise MCP server in PolicyLayer and add a rule for update_workorder: 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 Maximo Enterprise MCP. Nothing to install.
update_workorder 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 update_workorder 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 update_workorder. 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.
update_workorder is provided by the Maximo Enterprise MCP server (maximo-enterprise-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 →