delete-address
AI agents call delete-address to permanently remove resources in Terminal Shop MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting an address is irreversible and removes stored user data. This is more severe than Write (which is reversible) and qualifies as Destructive. While not financial in itself, it could disrupt customer operations if critical addresses are removed. High severity due to potential for user data loss; confidence slightly reduced due to missing description.
From the tool's definition Tool named 'delete-address' on a shopping/subscription management server. The 'delete-' prefix indicates irreversible deletion of user data (shipping address).
Attacks that exploit this kind of access
delete-address. It is categorised as a Destructive tool in the Terminal Shop MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Terminal Shop MCP Server MCP server in PolicyLayer and add a rule for delete-address: 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 Terminal Shop MCP Server. Nothing to install.
delete-address 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-address 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-address. 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-address is provided by the Terminal Shop MCP Server MCP server (pashaydev/terminal.shop.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 →