sell_token
AI agents use sell_token to commit financial operations through FourTrader MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Despite the empty description, the tool name 'sell_token' on a financial trading server that explicitly supports buy/sell operations for crypto tokens clearly indicates a financial transaction. Selling tokens on a blockchain is irreversible and commits financial obligations, making this Financial/critical severity. The sibling tool 'buy_token' and server context strongly confirm this classification.
From the tool's definition Tool name 'sell_token' on a server explicitly described as enabling 'buy/sell operations' for trading tokens on BNB Smart Chain; sibling tool 'buy_token' confirms this is a trading pair
Attacks that exploit this kind of access
sell_token. It is categorised as a Financial tool in the FourTrader MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the FourTrader MCP Server MCP server in PolicyLayer and add a rule for sell_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 FourTrader MCP Server. Nothing to install.
sell_token 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 sell_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 sell_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.
sell_token is provided by the FourTrader MCP Server MCP server (sunneeee/fourtrader-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 →