Get the current working directory.
AI agents call get_current_directory to retrieve information from Browser Automation 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 information about the current working directory path. It performs no modifications, does not execute code or commands, and has no destructive effects. It is a simple read operation with minimal security risk even in the context of browser automation or file system access tools.
From the tool's definition Tool name 'get_current_directory' and description 'Get the current working directory' indicate a query operation that retrieves filesystem state without modification or side effects.
Attacks that exploit this kind of access
Get the current working directory. It is categorised as a Read tool in the Browser Automation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Browser Automation 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 Browser Automation 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 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.
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 →