Purchase tokens from a Raydium Launchpad pool using the token mint address
AI agents use buy_token to commit financial operations through Raydium Launchlab — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool performs a real financial transaction on a blockchain DEX (Raydium), spending cryptocurrency to purchase tokens. It commits financial obligations and moves money, placing it firmly in the Financial category. The blast radius is critical as a misused tool could drain wallet funds by purchasing unwanted or malicious tokens.
From the tool's definition 'Purchase tokens from a Raydium Launchpad pool' — directly executes a financial transaction to acquire tokens using funds from the user's wallet
Attacks that exploit this kind of access
Purchase tokens from a Raydium Launchpad pool using the token mint address. It is categorised as a Financial tool in the Raydium Launchlab MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Raydium Launchlab MCP server in PolicyLayer and add a rule for buy_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 Raydium Launchlab. Nothing to install.
buy_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 buy_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 buy_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.
buy_token is provided by the Raydium Launchlab MCP server (kukapay/raydium-launchlab-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 →