Retire an asset by changing its status to DECOMMISSIONED. Requires manager role.
AI agents call retire_asset to permanently remove resources in Maximo Enterprise MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Retiring/decommissioning an asset is effectively irreversible in enterprise asset management systems; once marked DECOMMISSIONED, the asset is removed from active operations, maintenance schedules, and inventory, with no standard undo path. The required 'manager role' further underscores the high-impact, non-trivial nature of this action.
From the tool's definition 'Retire an asset by changing its status to DECOMMISSIONED' — decommissioning an asset is an irreversible status change that removes it from active service.
Attacks that exploit this kind of access
Retire an asset by changing its status to DECOMMISSIONED. Requires manager role. It is categorised as a Destructive tool in the Maximo Enterprise MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Maximo Enterprise MCP server in PolicyLayer and add a rule for retire_asset: 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.
retire_asset is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the retire_asset 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 retire_asset. 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.
retire_asset 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 →