get_provider_docs
AI agents call get_provider_docs 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 documentation about Terraform providers from the public registry. The verb 'get' combined with the context of a documentation-focused server indicates a read-only retrieval operation. Even with an empty tool description, the naming pattern and server purpose strongly suggest informational queries without data modification, creation, or deletion capabilities.
From the tool's definition Tool name 'get_provider_docs' and sibling tools named 'get_provider_data_source_docs', 'get_provider_resource_docs', 'get_provider_details', 'list_module_versions', 'search_modules' all indicate retrieval operations.
Attacks that exploit this kind of access
get_provider_docs. 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_docs: 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_docs 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_docs 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_docs. 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_docs 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 →