Low Risk

privateModuleSearch

privateModuleSearch

How to control privateModuleSearch ↓

AI agents call privateModuleSearch 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.

Low Risk

Search and lookup operations are Read operations—they retrieve data without side effects. No modification, deletion, execution, or financial impact is indicated by the name. The empty description prevents confirmation of any parameter injection or abuse vectors, but the naming pattern and server context support Read classification.

From the tool's definition Tool name 'privateModuleSearch' indicates a search/lookup operation against private Terraform modules. The description is empty, which lowers confidence slightly, but the name strongly suggests read-only querying.

Documented attack patterns abuse exactly the kind of access privateModuleSearch gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Terraform Registry MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for privateModuleSearch:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "privateModuleSearch": {}
  }
}

privateModuleSearch is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Terraform Registry MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the privateModuleSearch tool do? +

privateModuleSearch. It is categorised as a Read tool in the Terraform Registry MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on privateModuleSearch? +

Register the Terraform Registry MCP Server MCP server in PolicyLayer and add a rule for privateModuleSearch: 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.

What risk level is privateModuleSearch? +

privateModuleSearch is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit privateModuleSearch? +

Yes. Add a rate_limit block to the privateModuleSearch 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.

How do I block privateModuleSearch completely? +

Set action: deny in the PolicyLayer policy for privateModuleSearch. 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.

What MCP server provides privateModuleSearch? +

privateModuleSearch is provided by the Terraform Registry MCP Server MCP server (thrashr888/terraform-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Terraform Registry MCP Server tool call.

Deterministic rules across all 24 Terraform Registry MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

24 Terraform Registry MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.