AI agents use launchpad_build_sell to commit financial operations through Logiqical — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Selling tokens is a financial operation that moves assets and can result in irreversible financial loss if misused. The tool builds approve + sell transactions, which when broadcast will transfer/liquidate token holdings. On a trading infrastructure server, misuse could result in unintended asset liquidation at unfavorable prices or complete loss of token positions.
From the tool's definition 'sell a launchpad token (approve + sell)' — this tool constructs transactions to sell tokens on a trading launchpad, directly committing financial actions on Avalanche blockchain
Attacks that exploit this kind of access
Build unsigned txs to sell a launchpad token (approve + sell). It is categorised as a Financial tool in the Logiqical MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Logiqical MCP server in PolicyLayer and add a rule for launchpad_build_sell: 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 Logiqical. Nothing to install.
launchpad_build_sell 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 launchpad_build_sell 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 launchpad_build_sell. 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.
launchpad_build_sell is provided by the Logiqical MCP server (logiqical-mcp-server). 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 →