write_tf_configuration · Infrastructure Auto Provisioner MCP

WHAT IT DOES

What write_tf_configuration does on Infrastructure Auto Provisioner

AI agents use write_tf_configuration to create or update resources in Infrastructure Auto Provisioner — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Infrastructure Auto Provisioner environment.

WHY IT NEEDS A POLICY

Why write_tf_configuration needs a policy

This tool creates or modifies Terraform configuration files, which are declarative code that define infrastructure. While reversible (can be edited or redeployed), writing to configuration files is a significant action that could alter infrastructure state when applied.

From the tool's definition Tool name is 'write_tf_configuration' and description states 'Write a terraform configuration file'. The verb 'write' combined with modifying configuration files that control infrastructure provisioning represents a reversible modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

write_tf_configuration Rate-limited

write_tf_configuration stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "write_tf_configuration": {
      "limits": [
        {
          "counter": "write_tf_configuration_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Infrastructure Auto Provisioner, so you can run agents against it safely.

FAQ

Questions about write_tf_configuration

What does the write_tf_configuration tool do? +

Write a terraform configuration file. It is categorised as a Write tool in the Infrastructure Auto Provisioner MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on write_tf_configuration? +

Register the Infrastructure Auto Provisioner MCP server in PolicyLayer and add a rule for write_tf_configuration: 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 Infrastructure Auto Provisioner. Nothing to install.

What risk level is write_tf_configuration? +

write_tf_configuration is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit write_tf_configuration? +

Yes. Add a rate_limit block to the write_tf_configuration 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.

How do I block write_tf_configuration completely? +

Set action: deny in the PolicyLayer policy for write_tf_configuration. 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.

What MCP server provides write_tf_configuration? +

write_tf_configuration is provided by the Infrastructure Auto Provisioner MCP server (zerosync-co/mcp-server-autoprovisioner). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.