AI agents invoke createRun to trigger actions in Terraform Registry MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
In Terraform Cloud/Enterprise, a 'Run' initiates a plan or apply operation that provisions or modifies infrastructure. The sibling tools 'applyRun' and 'cancelRun' further confirm this is a Terraform run execution context. Creating a run triggers external infrastructure operations, placing it in the Execute category. Severity is high due to potential infrastructure changes.
From the tool's definition Tool name 'createRun' — 'Run' in Terraform context means triggering a plan/apply operation; no description provided to confirm or deny.
Documented attack patterns abuse exactly the kind of access createRun 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 createRun:
{
"version": "1",
"default": "deny",
"tools": {
"createRun": {
"limits": [
{
"counter": "createrun_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}createRun stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
createRun. It is categorised as a Execute tool in the Terraform Registry MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Terraform Registry MCP Server MCP server in PolicyLayer and add a rule for createRun: 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.
createRun is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the createRun 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 createRun. 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.
createRun 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.