Retire an IT asset (mark as disposed/retired). [Write]
AI agents use retire_asset to create or update resources in ServiceNow-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceNow-MCP environment.
Retiring an asset changes its status field reversibly (an asset can be un-retired or its status corrected if needed), making this a Write operation rather than Destructive. The severity is medium because misuse could incorrectly retire critical assets, disrupting asset management and compliance tracking, but the action is not financial and can be remediated.
From the tool's definition Tool description states 'Retire an IT asset (mark as disposed/retired)' — this marks an asset record with a retired/disposed status, modifying its state in ServiceNow without deleting the underlying record.
Attacks that exploit this kind of access
Retire an IT asset (mark as disposed/retired). [Write]. It is categorised as a Write tool in the ServiceNow-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ServiceNow- 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 ServiceNow-MCP. Nothing to install.
retire_asset 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 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 ServiceNow- MCP server (tedorigawa001/servicenow-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 →