AI agents call moduleSearch 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 |
|---|---|---|---|
query | string | — | Search query (e.g. 'vpc') |
keyword | string | — | Alternative search keyword (fallback if query not specified) |
provider | string | — | Filter modules by provider (e.g. 'aws') |
Parameters from the server's own tool schema.
The moduleSearch tool retrieves information from the Terraform Registry to help users discover modules matching their criteria. It has no side effects—it does not create, modify, delete, or execute code. It is purely informational, similar to a search engine or query interface.
From the tool's definition Tool description states 'Search for and recommend Terraform modules based on a query.' This performs search and recommendation operations without modifying any data.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Search for and recommend Terraform modules based on a query. It is categorised as a Read tool in the Terraform MCP Server, which means it retrieves data without modifying state.
moduleSearch accepts 3 parameters: query, keyword, provider. 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 moduleSearch: 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.
moduleSearch 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 moduleSearch 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 moduleSearch. 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.
moduleSearch 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 →