set_aztfexport_config
AI agents use set_aztfexport_config to create or update resources in Azure Terraform MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Azure Terraform MCP Server environment.
The 'set_' prefix strongly suggests this tool writes or modifies configuration state. 'aztfexport_config' implies it configures the aztfexport tool (Azure Terraform export utility). Configuration changes are reversible modifications to system state, fitting the Write category.
From the tool's definition Tool name contains 'set_' prefix combined with 'config' suffix, indicating configuration modification. Description is empty, limiting direct evidence of intent.
Attacks that exploit this kind of access
set_aztfexport_config. It is categorised as a Write tool in the Azure Terraform MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Azure Terraform MCP Server MCP server in PolicyLayer and add a rule for set_aztfexport_config: 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.
set_aztfexport_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_aztfexport_config 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 set_aztfexport_config. 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.
set_aztfexport_config 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 →