run_conftest_workspace_validation
AI agents invoke run_conftest_workspace_validation to trigger actions in Azure Terraform MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool runs conftest validation policies against a Terraform workspace. Even though validation itself is non-destructive, 'run_' indicates execution of an external tool/engine whose behavior depends on arguments and workspace state.
From the tool's definition Tool name contains 'run_' and 'validation' in the context of conftest, which is a policy-as-code framework that executes Rego policies against configuration files.
Attacks that exploit this kind of access
run_conftest_workspace_validation. It is categorised as a Execute tool in the Azure Terraform MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Azure Terraform MCP Server MCP server in PolicyLayer and add a rule for run_conftest_workspace_validation: 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.
run_conftest_workspace_validation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_conftest_workspace_validation 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 run_conftest_workspace_validation. 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.
run_conftest_workspace_validation 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 →