change_directory · Browser Automation MCP Server MCP

WHAT IT DOES

What change_directory does on Browser Automation MCP Server

AI agents invoke change_directory to trigger actions in Browser Automation 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 change_directory needs a policy

Changing the working directory is an execution-side-effect operation that alters the runtime environment state. While it doesn't delete data, it can affect subsequent file operations by redirecting them to a different directory, potentially causing unintended reads/writes elsewhere. The description is empty, so confidence is lowered.

From the tool's definition Tool name is 'change_directory'; description is empty or uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

change_directory Rate-limited

change_directory 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": {
    "change_directory": {
      "limits": [
        {
          "counter": "change_directory_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 Browser Automation MCP Server, so you can run agents against it safely.

FAQ

Questions about change_directory

What does the change_directory tool do? +

change_directory. It is categorised as a Execute tool in the Browser Automation 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 change_directory? +

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

What risk level is change_directory? +

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

Can I rate-limit change_directory? +

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

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

change_directory is provided by the Browser Automation MCP Server MCP server (raghu6798/browser_scrape_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.