transaction_simulate

Runs a read-only eth_call from the supplied address. It never signs or broadcasts a transaction and returns revert information when available.

SERVERAwesome Base SOURCEB5-Software/awesome-base-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/awesome-base-mcp/transaction-simulate.md

WHAT IT DOES

What transaction_simulate does on Awesome Base

AI agents call transaction_simulate 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.

RISK

Why transaction_simulate is rated Low

Simulates transaction execution without side effects; no data modification or financial impact.

From the tool's definition read-only eth_call, never signs or broadcasts transaction

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs transaction_simulate 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 transaction_simulate, this is the rule to start with:

transaction_simulate Allowed

transaction_simulate is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "transaction_simulate": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Awesome Base, apply this rule, and every transaction_simulate call is checked against it from then on.

FAQ

Questions about transaction_simulate

What does the transaction_simulate tool do? +

Runs a read-only eth_call from the supplied address. It never signs or broadcasts a transaction and returns revert information when available. It is categorised as a Read tool in the Awesome Base MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on transaction_simulate? +

Register the Awesome Base MCP server in PolicyLayer and add a rule for transaction_simulate: 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.

What risk level is transaction_simulate? +

transaction_simulate is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit transaction_simulate? +

Yes. Add a rate_limit block to the transaction_simulate 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.

How do I block transaction_simulate completely? +

Set action: deny in the PolicyLayer policy for transaction_simulate. 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.

What MCP server provides transaction_simulate? +

transaction_simulate 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.

KEEP EXPLORING

More on Awesome Base, and thousands of servers like it.

This server

All 44 Awesome Base tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →