sell_etf_token
AI agents use sell_etf_token to commit financial operations through Paloma DEX 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_etf_token' clearly indicates selling a financial instrument (ETF token) on a DEX. Given the server context of autonomous cross-chain trading, this tool likely executes a sell order committing financial assets. Selling tokens constitutes a financial operation with potentially irreversible market impact.
From the tool's definition Tool name 'sell_etf_token' on a DEX server described as enabling AI agents to 'autonomously execute cross-chain trading operations'.
Attacks that exploit this kind of access
sell_etf_token. It is categorised as a Financial tool in the Paloma DEX MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Paloma DEX MCP Server MCP server in PolicyLayer and add a rule for sell_etf_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 Paloma DEX MCP Server. Nothing to install.
sell_etf_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_etf_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_etf_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_etf_token is provided by the Paloma DEX MCP Server MCP server (volumefi/mcppadex). 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 →