simulate-transaction · Openfort MCP Server MCP

WHAT IT DOES

What simulate-transaction does on Openfort MCP Server

AI agents invoke simulate-transaction to trigger actions in Openfort MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why simulate-transaction needs a policy

Simulating a transaction intent involves executing a transaction workflow in a test/simulation context. While it may not move real funds, it interacts with wallet infrastructure and transaction pipelines, which could have side effects (e.g., state changes, resource consumption, or triggering real transactions depending on configuration).

From the tool's definition 'Simulates a new transaction intent' — triggers execution of a transaction simulation against the project infrastructure

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

simulate-transaction Rate-limited

simulate-transaction stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "simulate-transaction": {
      "limits": [
        {
          "counter": "simulate-transaction_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Openfort MCP Server, so you can run agents against it safely.

FAQ

Questions about simulate-transaction

What does the simulate-transaction tool do? +

Simulates a new transaction intent in the project. It is categorised as a Execute tool in the Openfort MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on simulate-transaction? +

Register the Openfort MCP Server MCP server in PolicyLayer and add a rule for simulate-transaction: 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 Openfort MCP Server. Nothing to install.

What risk level is simulate-transaction? +

simulate-transaction is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit simulate-transaction? +

Yes. Add a rate_limit block to the simulate-transaction 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 simulate-transaction completely? +

Set action: deny in the PolicyLayer policy for simulate-transaction. 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 simulate-transaction? +

simulate-transaction is provided by the Openfort MCP Server MCP server (openfort-xyz/-deprecated-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.