token_simulate_trade
Simulates an exact-input Uniswap V3 swap as a supplied trader to test the current transfer and router path without signing. The trader needs the input balance and router allowance for a meaningful sellability result.
This record as markdown: /tools/awesome-base-mcp/token-simulate-trade.md
What token_simulate_trade does on Awesome Base
AI agents call token_simulate_trade to retrieve information from Awesome Base without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why token_simulate_trade is rated Low
Simulates a trade only; no transaction is signed or submitted.
From the tool's definition Simulates...without signing
Attacks that exploit this kind of access
The rule that runs token_simulate_trade safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Awesome Base, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For token_simulate_trade, this is the rule to start with:
token_simulate_trade 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 Awesome Base, apply this rule, and every token_simulate_trade call is checked against it from then on.
Questions about token_simulate_trade
Simulates an exact-input Uniswap V3 swap as a supplied trader to test the current transfer and router path without signing. The trader needs the input balance and router allowance for a meaningful sellability result. It is categorised as a Read tool in the Awesome Base MCP Server, which means it retrieves data without modifying state.
Register the Awesome Base MCP server in PolicyLayer and add a rule for token_simulate_trade: 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 Awesome Base. Nothing to install.
token_simulate_trade 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 token_simulate_trade 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 token_simulate_trade. 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.
token_simulate_trade is provided by the Awesome Base MCP server (B5-Software/awesome-base-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Awesome Base, and thousands of servers like it.
This server
Across the catalogue