Updates an existing workspace
AI agents use edit-workspace to create or update resources in Terrakube MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Terrakube MCP Server environment.
This tool modifies reversible properties of a workspace (likely configuration, variables, settings, or other non-destructive attributes). While the blast radius could be significant in a production infrastructure context (a misconfigured workspace could disrupt services), the action is reversible—an incorrect update can be corrected by another update.
From the tool's definition Tool name 'edit-workspace' and description 'Updates an existing workspace' indicate modification of existing infrastructure state without deletion or destruction.
Attacks that exploit this kind of access
Updates an existing workspace. It is categorised as a Write tool in the Terrakube MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Terrakube MCP Server MCP server in PolicyLayer and add a rule for edit-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 Terrakube MCP Server. Nothing to install.
edit-workspace is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the edit-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 edit-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.
edit-workspace is provided by the Terrakube MCP Server MCP server (terrakube-io/mcp-server-terrakube). 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 →