Get the current run status for a Terraform Cloud workspace
AI agents call get_run_status to retrieve information from Terraform Cloud MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the status of an existing Terraform run—a read operation with no side effects. It does not execute, destroy, or modify infrastructure; it only queries the current state of a run. Low severity because status information is non-sensitive metadata and misuse poses minimal risk compared to execute or destructive operations.
From the tool's definition Tool name 'get_run_status' and description 'Get the current run status' indicate a query operation that retrieves information about run state without modifying or executing infrastructure.
Attacks that exploit this kind of access
Get the current run status for a Terraform Cloud workspace. It is categorised as a Read tool in the Terraform Cloud MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Terraform Cloud MCP Server MCP server in PolicyLayer and add a rule for get_run_status: 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 Cloud MCP Server. Nothing to install.
get_run_status 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_run_status 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_run_status. 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_run_status is provided by the Terraform Cloud MCP Server MCP server (matchs/tf-cloud-mcp-server). 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 →