search_modules
AI agents call search_modules 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.
search_modules searches the Terraform registry for module information. This is a read-only query operation that retrieves and displays data without modifying, deleting, or executing anything. The tool name and context of sibling read-only tools (list_module_versions, get_module_details, etc.) confirm this is a simple search/lookup function.
From the tool's definition Tool name 'search_modules' combined with sibling tools that all perform read-only operations (get_*, list_*, search_*). Server description explicitly states it 'search and retrieve information' with 'no side effects' implied by the retrieval-focused design.
Attacks that exploit this kind of access
search_modules. 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 search_modules: 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.
search_modules 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 search_modules 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 search_modules. 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.
search_modules 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 →