High Risk →

evaluate_mainworld

Execute JavaScript in the page

Part of the Camoufox server.

evaluate_mainworld can trigger actions in Camoufox, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE CAMOUFOX →

Free to start. No card required.

AI agents invoke evaluate_mainworld to trigger processes or run actions in Camoufox. 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.

evaluate_mainworld can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "evaluate_mainworld": {
      "limits": [
        {
          "counter": "evaluate_mainworld_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Camoufox policy for all 42 tools.

Get this rule live on your own Camoufox server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CAMOUFOX →

View all 42 tools →

These attack patterns abuse exactly the kind of access evaluate_mainworld gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so evaluate_mainworld only ever does what you allow.

SECURE CAMOUFOX →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the evaluate_mainworld tool do? +

Execute JavaScript in the page. It is categorised as a Execute tool in the Camoufox MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on evaluate_mainworld? +

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

What risk level is evaluate_mainworld? +

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

Can I rate-limit evaluate_mainworld? +

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

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

evaluate_mainworld is provided by the Camoufox MCP server (camoufox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Camoufox tool call.

Deterministic rules across all 42 Camoufox tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.