Delete an attachment
AI agents call attachment_delete to permanently remove resources in ServiceNow MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data (attachments) from ServiceNow with no undo capability. Destructive operations that erase records are inherently higher risk than Write (reversible modifications). In an enterprise ITSM context, accidental or malicious deletion of incident attachments, change documentation, or audit evidence could disrupt incident response and compliance.
From the tool's definition Tool name: 'attachment_delete' with description 'Delete an attachment' — the verb 'delete' is explicit and irreversible. Attachments in ITSM systems cannot be recovered once deleted.
Attacks that exploit this kind of access
Delete an attachment. It is categorised as a Destructive tool in the ServiceNow MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ServiceNow MCP Server MCP server in PolicyLayer and add a rule for attachment_delete: 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 Server. Nothing to install.
attachment_delete 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 attachment_delete 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 attachment_delete. 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.
attachment_delete is provided by the ServiceNow MCP Server MCP server (schwarztim/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 →