delete-card
AI agents call delete-card 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.
The 'delete' verb combined with the e-commerce context and presence of payment-related sibling tools (collect-card, create-card, create-token) strongly suggests this irreversibly removes a stored payment method. While the description is empty (lowering confidence slightly), the tool name and server purpose make the destructive nature clear.
From the tool's definition Tool name 'delete-card' indicates irreversible deletion of a stored payment card. Given the e-commerce context (Terminal.shop API for orders, subscriptions, payments), this permanently removes financial data.
Attacks that exploit this kind of access
delete-card. 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-card: 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-card 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-card 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-card. 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-card 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 →