solana_deploy_token
Deploy a new SPL token on Solana with custom name, symbol, decimals, and supply. Requires AGENTI_SOLANA_PRIVATE_KEY.
This record as markdown: /tools/nirholas-agenti/solana-deploy-token.md
What solana_deploy_token does on Agenti
AI agents use solana_deploy_token to commit financial operations through Agenti, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why solana_deploy_token is rated Critical
Deploying a token on a public blockchain is a financial operation that irreversibly commits on-chain resources, consumes SOL (gas/rent), and creates a new financial instrument.
From the tool's definition Deploy a new SPL token on Solana with custom name, symbol, decimals, and supply. Requires AGENTI_SOLANA_PRIVATE_KEY.
Attacks that exploit this kind of access
The rule that runs solana_deploy_token safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agenti, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For solana_deploy_token, this is the rule to start with:
Any call to solana_deploy_token is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Agenti, apply this rule, and every solana_deploy_token call is checked against it from then on.
Questions about solana_deploy_token
Deploy a new SPL token on Solana with custom name, symbol, decimals, and supply. Requires AGENTI_SOLANA_PRIVATE_KEY. It is categorised as a Financial tool in the Agenti MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Agenti MCP server in PolicyLayer and add a rule for solana_deploy_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 Agenti. Nothing to install.
solana_deploy_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 solana_deploy_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 solana_deploy_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.
solana_deploy_token is provided by the Agenti MCP server (nirholas/agenti). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agenti, and thousands of servers like it.
Across the catalogue