execute_transaction · Telos Network MCP Server MCP

WHAT IT DOES

What execute_transaction does on Telos Network MCP Server

AI agents invoke execute_transaction to trigger actions in Telos Network 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 execute_transaction needs a policy

While this could be classified as Financial (since it executes transactions on a DeFi platform), the Execute category is more precise because the tool's primary function is to execute/run prepared transactions whose effects depend on the transaction arguments. The Financial impact is a consequence of execution, not the mechanism itself.

From the tool's definition Tool name 'execute_transaction' combined with description 'Execute a prepared transaction' indicates the tool runs blockchain transactions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_transaction Rate-limited

execute_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": {
    "execute_transaction": {
      "limits": [
        {
          "counter": "execute_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 Telos Network MCP Server, so you can run agents against it safely.

FAQ

Questions about execute_transaction

What does the execute_transaction tool do? +

Execute a prepared transaction (for interactive mode). It is categorised as a Execute tool in the Telos Network 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 execute_transaction? +

Register the Telos Network MCP Server MCP server in PolicyLayer and add a rule for execute_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 Telos Network MCP Server. Nothing to install.

What risk level is execute_transaction? +

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

Can I rate-limit execute_transaction? +

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

Set action: deny in the PolicyLayer policy for execute_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 execute_transaction? +

execute_transaction is provided by the Telos Network MCP Server MCP server (tairon-ai/telos-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.