// SCAN REPORT

Terraform Registry MCP Server

24 tools. 5 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 11 Jun 2026

5 can modify or destroy data

19 read-only

24 tools total

Community server · catalogue entry verified 11/06/2026

How to control Terraform Registry MCP Server ↓

TOOL MAP

Read (19) Write / Execute (4) Destructive / Financial (1)

MOST DANGEROUS TOOLS

Critical Risk

Destructive · High cancelRun Based on the tool name, 'cancelRun' likely cancels an in-progress Terraform run, which is an irreversible action that terminates an active operation. Execute · High applyRun In Terraform, 'apply' executes planned infrastructure changes, provisioning or modifying real resources. Execute · High createRun In Terraform Cloud/Enterprise, a 'Run' initiates a plan or apply operation that provisions or modifies infrastructure. Execute · High unlockWorkspace Unlocking a workspace in Terraform/TFC triggers an operational state change that allows runs to proceed; it is an external operational action rather than a simple data read or write.

5 of Terraform Registry MCP Server's 24 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

HOW TO CONTROL TERRAFORM REGISTRY MCP SERVER

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. These are the rules we recommend:

Deny destructive operations

{
  "cancelRun": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "lockWorkspace": {
    "limits": [
      {
        "counter": "lockworkspace_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "runDetails": {
    "limits": [
      {
        "counter": "rundetails_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Terraform Registry MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON TERRAFORM REGISTRY →

Free to start. No card required.

ALL 24 TERRAFORM REGISTRY MCP SERVER TOOLS

DESTRUCTIVE 1 tools

Destructive cancelRun cancelRun

EXECUTE 3 tools

Execute applyRun applyRun Execute createRun createRun Execute unlockWorkspace unlockWorkspace

WRITE 1 tools

Write lockWorkspace lockWorkspace

READ 19 tools

Read runDetails runDetails Read explorerQuery explorerQuery Read functionDetails functionDetails Read listDataSources listDataSources Read listOrganizations listOrganizations Read listRuns listRuns Read listWorkspaceResources listWorkspaceResources Read listWorkspaces listWorkspaces Read moduleDetails moduleDetails Read moduleSearch moduleSearch Read policyDetails policyDetails Read policySearch policySearch Read privateModuleDetails privateModuleDetails Read privateModuleSearch privateModuleSearch Read providerDetails providerDetails Read providerGuides providerGuides Read resourceArgumentDetails resourceArgumentDetails Read resourceUsage resourceUsage Read workspaceDetails workspaceDetails

RELATED SERVERS

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Can an AI agent delete data through the Terraform Registry MCP Server MCP server? +

Yes. The Terraform Registry MCP Server server exposes 1 destructive tools including cancelRun. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Terraform Registry MCP Server? +

The Terraform Registry MCP Server server has 1 write tools including lockWorkspace. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Terraform Registry MCP Server.

How many tools does the Terraform Registry MCP Server MCP server expose? +

24 tools across 4 categories: Destructive, Execute, Read, Write. 19 are read-only. 5 can modify, create, or delete data.

How do I enforce a policy on Terraform Registry MCP Server? +

Register the Terraform Registry MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Terraform Registry MCP Server tool call.

Deterministic rules across all 24 Terraform Registry MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON TERRAFORM REGISTRY →

Free to start. No card required.

24 Terraform Registry MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

Terraform Registry MCP Server

// TOOL MAP

// MOST DANGEROUS TOOLS

// HOW TO CONTROL TERRAFORM REGISTRY MCP SERVER

// ALL 24 TERRAFORM REGISTRY MCP SERVER TOOLS

// RELATED SERVERS

// FAQ