This record as markdown: /tools/agentics-ai-code-mcp/get-workspace.md
What get_workspace does on Code MCP Server
AI agents call get_workspace to retrieve information from Code MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_workspace is rated Low
This tool retrieves metadata about the workspace configuration. It performs a simple query operation that returns existing information without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an attacker could only learn the workspace path, which is already accessible through normal means. This is a straightforward Read operation.
From the tool's definition Tool name 'get_workspace' and description 'Get current workspace path' indicate a retrieval operation with no side effects. Returns information about the current working directory without modifying any state.
Attacks that exploit this kind of access
The rule that runs get_workspace safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Code MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_workspace, this is the rule to start with:
get_workspace is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Code MCP Server, apply this rule, and every get_workspace call is checked against it from then on.
Questions about get_workspace
Get current workspace path. It is categorised as a Read tool in the Code MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Code MCP Server MCP server in PolicyLayer and add a rule for get_workspace: 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 Code MCP Server. Nothing to install.
get_workspace 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_workspace 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_workspace. 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_workspace is provided by the Code MCP Server MCP server (agentics-ai/code-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Code MCP Server, and thousands of servers like it.
This server
Across the catalogue