AI agents use lockWorkspace to create or update resources in Terraform Registry MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Terraform Registry MCP Server environment.
Locking a workspace in Terraform Cloud/Enterprise prevents further runs and modifications. Based on the name, this is a Write operation (modifying workspace state reversibly, as workspaces can be unlocked). It has high severity because locking a workspace can block CI/CD pipelines and prevent infrastructure changes. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'lockWorkspace' — description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access lockWorkspace gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Terraform Registry MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for lockWorkspace:
{
"version": "1",
"default": "deny",
"tools": {
"lockWorkspace": {
"limits": [
{
"counter": "lockworkspace_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}lockWorkspace stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
lockWorkspace. It is categorised as a Write tool in the Terraform Registry MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Terraform Registry MCP Server MCP server in PolicyLayer and add a rule for lockWorkspace: 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 Terraform Registry MCP Server. Nothing to install.
lockWorkspace 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 lockWorkspace 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 lockWorkspace. 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.
lockWorkspace is provided by the Terraform Registry MCP Server MCP server (thrashr888/terraform-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 24 Terraform Registry MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
24 Terraform Registry MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.