create_token
Deploy a new TIP-20 token on Tempo blockchain via the factory contract.
This record as markdown: /tools/arome3-tempo-mcp/create-token.md
What create_token does on Tempo
AI agents use create_token to commit financial operations through Tempo, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why create_token is rated Critical
Deploying a new token on a blockchain is a financial operation that creates a new on-chain financial instrument. It has real-world financial implications (token issuance, potential value creation/transfer), is irreversible once deployed, and exists on a stablecoin payments blockchain explicitly designed for 'real-world payments'.
From the tool's definition Deploy a new TIP-20 token on Tempo blockchain via the factory contract
Attacks that exploit this kind of access
The rule that runs create_token safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tempo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_token, this is the rule to start with:
Any call to create_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 Tempo, apply this rule, and every create_token call is checked against it from then on.
Questions about create_token
Deploy a new TIP-20 token on Tempo blockchain via the factory contract. It is categorised as a Financial tool in the Tempo MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Tempo MCP server in PolicyLayer and add a rule for create_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 Tempo. Nothing to install.
create_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 create_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 create_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.
create_token is provided by the Tempo MCP server (arome3/tempo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tempo, and thousands of servers like it.
Across the catalogue