Delete an attachment from a record (requires WRITE_ENABLED=true)
AI agents call delete_attachment to permanently remove resources in ServiceNow-MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes an attachment, which cannot be undone. Although attachments are typically lower-risk than core record data, deletion is irreversible and constitutes a destructive action. The requirement for WRITE_ENABLED=true indicates it's a sensitive operation. Destructive is more severe than Write, so it takes precedence over the write capability needed to execute it.
From the tool's definition The tool name is 'delete_attachment' and the description states it will 'Delete an attachment from a record'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete an attachment from a record (requires WRITE_ENABLED=true). It is categorised as a Destructive tool in the ServiceNow-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ServiceNow- MCP server in PolicyLayer and add a rule for delete_attachment: 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.
delete_attachment 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_attachment 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_attachment. 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_attachment 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 →