AI agents call moduleDetails to retrieve information from Terraform without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
module | string | Yes | Module name (e.g. 'vpc') |
provider | string | Yes | Provider name (e.g. 'aws') |
namespace | string | Yes | Module namespace (e.g. 'terraform-aws-modules') |
Parameters from the server's own tool schema.
This tool queries and returns information about Terraform modules from the registry without creating, modifying, deleting, or executing any infrastructure changes. It is purely informational retrieval with no side effects, fitting the Read category. The low severity reflects that metadata queries pose minimal risk even if misused by an AI agent.
From the tool's definition Tool description states it 'Retrieves detailed metadata' for Terraform modules including versions, inputs, outputs, and dependencies. The verb 'Retrieves' and the focus on querying metadata without modification indicates a read-only operation.
Attacks that exploit this kind of access
Retrieves detailed metadata for a Terraform module including versions, inputs, outputs, and dependencies. It is categorised as a Read tool in the Terraform MCP Server, which means it retrieves data without modifying state.
moduleDetails accepts 3 parameters: module, provider, namespace. Required: module, provider, namespace. The full parameter table on this page comes from the server's own tool schema.
Register the Terraform MCP server in PolicyLayer and add a rule for moduleDetails: 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. Nothing to install.
moduleDetails 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 moduleDetails 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 moduleDetails. 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.
moduleDetails is provided by the Terraform MCP server (terraform-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 →