opera_do · Opera DevTools MCP: Risk & Policy

WHAT IT DOES

What opera_do does on Opera DevTools MCP

AI agents invoke opera_do to trigger actions in Opera DevTools MCP. 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 opera_do needs a policy

The tool name 'opera_do' and description 'Instruct Opera' suggest it issues instructions/commands to the Opera browser, triggering external operations. Given the sibling tools context (click, drag, evaluate_script, execute tools), this likely executes browser actions or commands.

From the tool's definition 'Instruct Opera' — triggers browser-level actions in Opera

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

opera_do Rate-limited

opera_do 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": {
    "opera_do": {
      "limits": [
        {
          "counter": "opera_do_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 Opera DevTools MCP, so you can run agents against it safely.

FAQ

Questions about opera_do

What does the opera_do tool do? +

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

How do I enforce a policy on opera_do? +

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

What risk level is opera_do? +

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

Can I rate-limit opera_do? +

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

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

opera_do is provided by the Opera DevTools MCP server (operasoftware/opera-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.