Xóa asset
AI agents call delete_asset to permanently remove resources in ServiceDesk Plus MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of assets is an irreversible destructive action that removes data permanently from the system. While not as critical as financial transactions, the loss of CMDB asset records can disrupt IT operations, asset tracking, and business continuity. High severity reflects the potential impact on organizational IT infrastructure documentation.
From the tool's definition Tool name is 'delete_asset' and description states 'Xóa asset' (Vietnamese for 'Delete asset'). This tool performs an irreversible deletion operation on asset records in the CMDB.
Attacks that exploit this kind of access
Xóa asset. It is categorised as a Destructive tool in the ServiceDesk Plus MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ServiceDesk Plus MCP Server MCP server in PolicyLayer and add a rule for delete_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 ServiceDesk Plus MCP Server. Nothing to install.
delete_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 delete_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 delete_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.
delete_asset is provided by the ServiceDesk Plus MCP Server MCP server (thichcode/servicedeskplus_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 →