estimate_fee_swap
Estimate the output amount for a fee token swap. The Fee AMM uses a fixed rate
This record as markdown: /tools/arome3-tempo-mcp/estimate-fee-swap.md
What estimate_fee_swap does on Tempo
AI agents call estimate_fee_swap to retrieve information from Tempo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why estimate_fee_swap is rated Low
This tool performs a calculation/estimation of swap output amounts without actually executing a swap, modifying balances, or committing any transactions. It is purely informational, similar to a price quote or simulation. Even in the context of a payment/blockchain system, estimation functions that do not execute transactions or alter state are classified as Read operations.
From the tool's definition Tool name 'estimate_fee_swap' and description 'Estimate the output amount for a fee token swap' indicate a read-only query operation that returns calculated values without executing or modifying state.
Attacks that exploit this kind of access
The rule that runs estimate_fee_swap 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 estimate_fee_swap, this is the rule to start with:
estimate_fee_swap is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tempo, apply this rule, and every estimate_fee_swap call is checked against it from then on.
Questions about estimate_fee_swap
Estimate the output amount for a fee token swap. The Fee AMM uses a fixed rate. It is categorised as a Read tool in the Tempo MCP Server, which means it retrieves data without modifying state.
Register the Tempo MCP server in PolicyLayer and add a rule for estimate_fee_swap: 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.
estimate_fee_swap is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the estimate_fee_swap 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 estimate_fee_swap. 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.
estimate_fee_swap 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.
This server
Across the catalogue