create-subscription
AI agents use create-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.
Creating a subscription commits the user to recurring financial obligations. The server context (Terminal.shop, payments, orders) and sibling tools strongly indicate this tool initiates a recurring payment arrangement. Despite the empty description, the name and context make this a Financial categorization with high confidence.
From the tool's definition Tool name 'create-subscription' on a server described as handling 'subscriptions through Terminal.shop's API'; sibling tools include 'cancel-subscription', 'checkout', 'create-order' indicating financial operations.
Attacks that exploit this kind of access
create-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 create-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.
create-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 create-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 create-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.
create-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 →