High Risk →

tl_evaluate

Execute JavaScript in the browser page context. Useful for DOM manipulation, scrolling, reading state, or any operation not covered by other tools. Returns the serialized result.

Accepts freeform code/query input (script)

Part of the Tronlink MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents invoke tl_evaluate to trigger processes or run actions in Tronlink. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

tl_evaluate can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

tronlink.yaml
tools:
  tl_evaluate:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Tronlink policy for all 55 tools.

Tool Name tl_evaluate
Category Execute
MCP Server Tronlink MCP Server
Risk Level High

View all 55 tools →

Agents calling execute-class tools like tl_evaluate have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

tl_evaluate is one of the high-risk operations in Tronlink. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the tl_evaluate tool do? +

Execute JavaScript in the browser page context. Useful for DOM manipulation, scrolling, reading state, or any operation not covered by other tools. Returns the serialized result.. It is categorised as a Execute tool in the Tronlink MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on tl_evaluate? +

Add a rule in your Intercept YAML policy under the tools section for tl_evaluate. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Tronlink MCP server.

What risk level is tl_evaluate? +

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

Can I rate-limit tl_evaluate? +

Yes. Add a rate_limit block to the tl_evaluate rule in your Intercept 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 tl_evaluate completely? +

Set action: deny in the Intercept policy for tl_evaluate. 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 tl_evaluate? +

tl_evaluate is provided by the Tronlink MCP server (@tronlink/mcp-server-tronlink). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Tronlink

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.