This record as markdown: /tools/io-github-dave-london-git/workspace.md
What workspace does on Git
AI agents call workspace to permanently remove resources in Git, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why workspace is rated Critical
The tool can delete Terraform workspaces, which is an irreversible destructive action. Terraform workspaces contain state data; deleting one removes that state permanently. Since the tool spans multiple categories (Read for list, Write for create/select, Destructive for delete), the most severe applicable category — Destructive — is assigned.
From the tool's definition 'delete workspaces' — workspace deletion is irreversible; also covers create (Write) and select/list (Read), but most severe applicable category is Destructive
Attacks that exploit this kind of access
The rule that runs workspace safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Git, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For workspace, this is the rule to start with:
workspace is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Git, apply this rule, and every workspace call is checked against it from then on.
Questions about workspace
Manages Terraform workspaces: list, select, create, or delete workspaces. It is categorised as a Destructive tool in the Git MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Git MCP server in PolicyLayer and add a rule for 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 Git. Nothing to install.
workspace is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the 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 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.
workspace is provided by the Git MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Git, and thousands of servers like it.
Across the catalogue