Get the current working directory for a connection
AI agents call ssh_get_working_directory to retrieve information from SSH MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves the current working directory path from a remote SSH connection. It has no side effects, does not modify data, execute code, delete resources, or move money. It is a straightforward read operation on connection metadata. Severity is low because the information retrieved (a directory path) is typically non-sensitive and provides minimal value for exploitation.
From the tool's definition Tool name is 'ssh_get_working_directory' and description states 'Get the current working directory for a connection' — a pure query operation that retrieves information without modifying any state.
Attacks that exploit this kind of access
Get the current working directory for a connection. It is categorised as a Read tool in the SSH MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SSH MCP Server MCP server in PolicyLayer and add a rule for ssh_get_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 SSH MCP Server. Nothing to install.
ssh_get_working_directory is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ssh_get_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.
Set action: deny in the PolicyLayer policy for ssh_get_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.
ssh_get_working_directory is provided by the SSH MCP Server MCP server (widjis/mcp-ssh). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →