cancel-subscription
AI agents use cancel-subscription to commit financial operations through Terminal Shop MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Cancelling a subscription is a financial action that terminates a recurring financial commitment. While the description is empty (lowering confidence slightly), the tool name combined with the server context (e-commerce/subscription management) clearly indicates this modifies an active financial arrangement. It is also partially destructive/irreversible as cancelled subscriptions may not be easily reinstated.
From the tool's definition Tool name 'cancel-subscription' on a server described as handling 'subscriptions through Terminal.shop's API'
Attacks that exploit this kind of access
cancel-subscription. It is categorised as a Financial tool in the Terminal Shop MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Terminal Shop MCP Server MCP server in PolicyLayer and add a rule for cancel-subscription: 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.
cancel-subscription is a Financial 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 cancel-subscription 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 cancel-subscription. 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.
cancel-subscription 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 →