AI agents call get_current_directory to retrieve information from Windows CLI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of the current working directory path. It has no side effects, does not execute commands, does not modify or delete data, and does not move money. While it operates on a Windows CLI server that has Execute capabilities via sibling tools, this specific tool is purely informational and retrieves existing state.
From the tool's definition Tool name is 'get_current_directory' and description states 'Get the current working directory' - this retrieves filesystem metadata without modifying, deleting, or executing code.
Documented attack patterns abuse exactly the kind of access get_current_directory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Windows CLI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_current_directory:
{
"version": "1",
"default": "deny",
"tools": {
"get_current_directory": {}
}
}get_current_directory is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the current working directory. It is categorised as a Read tool in the Windows CLI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Windows CLI MCP Server MCP server in PolicyLayer and add a rule for get_current_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 Windows CLI MCP Server. Nothing to install.
get_current_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 get_current_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 get_current_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.
get_current_directory is provided by the Windows CLI MCP Server MCP server (simon-ami/win-cli-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 Windows CLI MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
5 Windows CLI MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.