set_working_directory · MCP Merge Request Summarizer MCP

WHAT IT DOES

What set_working_directory does on MCP Merge Request Summarizer

AI agents use set_working_directory to create or update resources in MCP Merge Request Summarizer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Merge Request Summarizer environment.

WHY IT NEEDS A POLICY

Why set_working_directory needs a policy

This tool modifies the operational context of the server by setting a working directory. While it doesn't directly create or delete data, it changes mutable state that determines which files and repositories subsequent tools will access. This is a reversible modification (the working directory can be changed again), placing it in Write rather than Execute.

From the tool's definition Tool description states 'Set the working directory context' - this modifies server state by changing which directory the server operates within, affecting subsequent tool behavior.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_working_directory Rate-limited

set_working_directory stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_working_directory": {
      "limits": [
        {
          "counter": "set_working_directory_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Merge Request Summarizer, so you can run agents against it safely.

FAQ

Questions about set_working_directory

What does the set_working_directory tool do? +

Set the working directory context for the MCP server. It is categorised as a Write tool in the MCP Merge Request Summarizer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_working_directory? +

Register the MCP Merge Request Summarizer MCP server in PolicyLayer and add a rule for set_working_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 MCP Merge Request Summarizer. Nothing to install.

What risk level is set_working_directory? +

set_working_directory is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_working_directory? +

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

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

set_working_directory is provided by the MCP Merge Request Summarizer MCP server (sonicjoy/mcp_merge_request_summarizer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.