ssh_set_working_directory · MCP SSH Server MCP

WHAT IT DOES

What ssh_set_working_directory does on MCP SSH Server

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

WHY IT NEEDS A POLICY

Why ssh_set_working_directory needs a policy

This tool modifies the state of an SSH connection by changing its working directory. It is a reversible configuration change (can be changed back), so it falls under Write rather than Execute or Destructive. The blast radius is low since it only affects the working directory context for subsequent commands on that connection.

From the tool's definition Set the current working directory for a connection

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ssh_set_working_directory Rate-limited

ssh_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": {
    "ssh_set_working_directory": {
      "limits": [
        {
          "counter": "ssh_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 SSH Server, so you can run agents against it safely.

FAQ

Questions about ssh_set_working_directory

What does the ssh_set_working_directory tool do? +

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

How do I enforce a policy on ssh_set_working_directory? +

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

What risk level is ssh_set_working_directory? +

ssh_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 ssh_set_working_directory? +

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

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

ssh_set_working_directory is provided by the MCP SSH Server MCP server (mahathirmuh/mcp-ssh-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

ssh_set_working_directory is one line of MCP SSH Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →