tf_apply · RedisNexus MCP: Risk & Policy

WHAT IT DOES

What tf_apply does on RedisNexus

AI agents invoke tf_apply to trigger actions in RedisNexus. 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.

WHY IT NEEDS A POLICY

Why tf_apply needs a policy

Terraform apply executes infrastructure-as-code changes that can create, modify, or destroy cloud resources at scale. While it requires confirmation, misuse by an AI agent could result in massive infrastructure changes including resource deletion, making this critical severity.

From the tool's definition 'Apply Terraform changes' — applying Terraform provisions, modifies, or destroys infrastructure resources based on configuration

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tf_apply Rate-limited

tf_apply stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tf_apply": {
      "limits": [
        {
          "counter": "tf_apply_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about tf_apply

What does the tf_apply tool do? +

Apply Terraform changes. Requires confirmation. It is categorised as a Execute tool in the RedisNexus MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on tf_apply? +

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

What risk level is tf_apply? +

tf_apply is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit tf_apply? +

Yes. Add a rate_limit block to the tf_apply 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 tf_apply completely? +

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

tf_apply is provided by the RedisNexus MCP server (rajkumar-madhu/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.