get_provider_details
AI agents call get_provider_details 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 retrieves provider details from the Terraform registry, a read-only operation that queries and returns data without modifying, executing, or deleting anything. The empty description slightly reduces confidence, but the naming convention and server context strongly indicate a simple data retrieval function consistent with other Read-category tools on this server.
From the tool's definition Tool name 'get_provider_details' follows the pattern of sibling tools (get_latest_module_version, get_provider_docs, get_provider_resource_docs) which are all retrieval operations.
Attacks that exploit this kind of access
get_provider_details. 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 get_provider_details: 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.
get_provider_details 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 get_provider_details 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 get_provider_details. 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.
get_provider_details 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 →