search_providers
AI agents call search_providers 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 searches the Terraform registry for provider information—a pure query operation with no side effects. It retrieves data without modifying, executing code, or creating obligations. Consistent with other Read-category tools on this server (search_modules, list_provider_versions, get_provider_details, etc.). Low severity because misuse has no destructive or operational impact.
From the tool's definition Tool name 'search_providers' combined with server purpose of 'search and retrieve information about Terraform providers' and sibling tools that all perform read operations (get_latest_*, list_*, search_modules).
Attacks that exploit this kind of access
search_providers. 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_providers: 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_providers 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_providers 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_providers. 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_providers 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 →