browser_interact · AutoDev MCP: Risk & Policy

WHAT IT DOES

What browser_interact does on AutoDev MCP

AI agents invoke browser_interact to trigger actions in AutoDev 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 browser_interact needs a policy

This tool triggers real browser interactions (click, type, fill, press, select) whose effects depend entirely on arguments and context. These actions can submit forms, trigger purchases, modify application state, or perform any number of operations in a live browser session. Since the effects are argument-dependent and can be wide-ranging, Execute is the appropriate category.

From the tool's definition Perform click/type/fill/press/select interactions in browser session

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_interact Rate-limited

browser_interact 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": {
    "browser_interact": {
      "limits": [
        {
          "counter": "browser_interact_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 AutoDev MCP, so you can run agents against it safely.

FAQ

Questions about browser_interact

What does the browser_interact tool do? +

Perform click/type/fill/press/select interactions in browser session. It is categorised as a Execute tool in the AutoDev 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 browser_interact? +

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

What risk level is browser_interact? +

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

Can I rate-limit browser_interact? +

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

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

browser_interact is provided by the AutoDev MCP server (rookiejefren/autocoding-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.