collect-card
AI agents use collect-card 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.
The tool name 'collect-card' strongly implies capturing or storing payment card information, which is a financial operation. Given the server context (e-commerce with payment processing) and sibling tools like 'create-card', 'checkout', and 'create-order', this tool likely collects credit card details to facilitate payments. The description is empty, reducing confidence, but the financial context is clear.
From the tool's definition Tool name 'collect-card' on a server that handles payments, orders, and subscriptions via Terminal.shop's API; sibling tools include 'create-card', 'checkout', 'create-order', 'create-subscription'
Attacks that exploit this kind of access
collect-card. 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 collect-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.
collect-card 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 collect-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 collect-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.
collect-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 →