add_fee_liquidity
Add liquidity to a Fee AMM pool. You must provide equal USD value of both tokens.
This record as markdown: /tools/arome3-tempo-mcp/add-fee-liquidity.md
What add_fee_liquidity does on Tempo
AI agents use add_fee_liquidity to commit financial operations through Tempo, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why add_fee_liquidity is rated Critical
This tool commits real financial assets (tokens of equal USD value) to an AMM liquidity pool on a blockchain. This is a financial operation that moves or locks user funds, fitting the Financial category. Misuse by an AI agent could result in significant financial loss or unintended capital deployment.
From the tool's definition Add liquidity to a Fee AMM pool. You must provide equal USD value of both tokens.
Attacks that exploit this kind of access
The rule that runs add_fee_liquidity 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 add_fee_liquidity, this is the rule to start with:
Any call to add_fee_liquidity 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 add_fee_liquidity call is checked against it from then on.
Questions about add_fee_liquidity
Add liquidity to a Fee AMM pool. You must provide equal USD value of both tokens. 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 add_fee_liquidity: 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.
add_fee_liquidity 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 add_fee_liquidity 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 add_fee_liquidity. 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.
add_fee_liquidity 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