check_tflint_installation
AI agents call check_tflint_installation to retrieve information from Azure Terraform MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to check whether tflint (a Terraform linter) is installed on the system. Such checks are diagnostic queries that retrieve information about the environment without modifying, executing code, or deleting resources.
From the tool's definition Tool name 'check_tflint_installation' indicates a verification/diagnostic operation. The verb 'check' combined with 'installation' suggests querying the status of an installed linter tool, with no side effects on system state.
Attacks that exploit this kind of access
check_tflint_installation. It is categorised as a Read tool in the Azure Terraform MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Azure Terraform MCP Server MCP server in PolicyLayer and add a rule for check_tflint_installation: 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 Azure Terraform MCP Server. Nothing to install.
check_tflint_installation 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 check_tflint_installation 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 check_tflint_installation. 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.
check_tflint_installation is provided by the Azure Terraform MCP Server MCP server (liuwuliuyun/tf-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 →