AI agents call runDetails to retrieve information from Terraform Registry MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'runDetails' strongly implies a read/query operation to fetch information about a Terraform run, consistent with sibling tools like 'listRuns' and 'listWorkspaces' which are also read-oriented. However, the empty description lowers confidence. No evidence of side effects, so Read is the best classification.
From the tool's definition Tool name 'runDetails' suggests retrieval of details about a run; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access runDetails 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 runDetails:
{
"version": "1",
"default": "deny",
"tools": {
"runDetails": {}
}
}runDetails is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
runDetails. It is categorised as a Read tool in the Terraform Registry MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Terraform Registry MCP Server MCP server in PolicyLayer and add a rule for runDetails: 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.
runDetails 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 runDetails 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 runDetails. 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.
runDetails 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.