List all available versions of a Terraform module.
AI agents call list_module_versions 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.
This tool queries and returns version information from the public Terraform registry without modifying, executing, or destructing any data. It is a straightforward informational lookup with no blast radius if misused by an AI agent—the worst outcome would be retrieving irrelevant or outdated version lists.
From the tool's definition Tool name 'list_module_versions' and description 'List all available versions of a Terraform module' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all available versions of a Terraform module. 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 list_module_versions: 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.
list_module_versions 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 list_module_versions 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 list_module_versions. 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.
list_module_versions is provided by the Terraform Registry MCP Server MCP server (qvakk/terraform-registry-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 →