Create a bonding-curve based token on Raydium Launchpad
AI agents use mint_token to commit financial operations through Raydium Launchlab — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Minting a token on Raydium Launchpad involves deploying a smart contract and establishing a bonding curve, which is a financial operation with real on-chain consequences. It commits funds (e.g., SOL for deployment fees and initial liquidity), creates a permanent on-chain asset, and exposes users to financial risk.
From the tool's definition 'Create a bonding-curve based token on Raydium Launchpad' — minting a token on a DeFi launchpad with a bonding curve commits financial resources and creates a tradeable on-chain asset
Attacks that exploit this kind of access
Create a bonding-curve based token on Raydium Launchpad. 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 mint_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.
mint_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 mint_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 mint_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.
mint_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 →