create-token
AI agents call create-token as a supporting operation in Terminal Shop MCP Server workflows.
The description is empty, so the exact behavior is unknown. Based on the name 'create-token', it likely creates an authentication or API token (a Write operation), but in a financial/e-commerce context it could relate to payment tokenization. Without more information, confidence is low.
From the tool's definition Tool name is 'create-token' and description is empty or uninformative.
Attacks that exploit this kind of access
create-token. It is categorised as a Other tool in the Terminal Shop MCP Server MCP Server, which means it performs auxiliary operations.
Register the Terminal Shop MCP Server MCP server in PolicyLayer and add a rule for create-token: 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-token is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the create-token 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-token. 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-token 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 →