generate_infrastructure_code · Awslabs Valkey MCP

WHAT IT DOES

What generate_infrastructure_code does on Awslabs Valkey

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

WHY IT NEEDS A POLICY

Why generate_infrastructure_code needs a policy

The tool generates infrastructure code, which is a reversible write operation—it creates or modifies configuration/code artifacts that can be reviewed, edited, or deleted. This is Write-class severity (medium) rather than Execute because generation itself does not immediately apply the code to live infrastructure.

From the tool's definition Tool name 'generate_infrastructure_code' indicates code generation; sibling tools show this server manages infrastructure (add_inline_policy, add_user_to_group, aggregate) and AWS operations. The 'generate' action creates new artifacts (infrastructure code).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_infrastructure_code Rate-limited

generate_infrastructure_code 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": {
    "generate_infrastructure_code": {
      "limits": [
        {
          "counter": "generate_infrastructure_code_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 Awslabs Valkey, so you can run agents against it safely.

FAQ

Questions about generate_infrastructure_code

What does the generate_infrastructure_code tool do? +

generate_infrastructure_code. It is categorised as a Write tool in the Awslabs Valkey MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_infrastructure_code? +

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

What risk level is generate_infrastructure_code? +

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

Can I rate-limit generate_infrastructure_code? +

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

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

generate_infrastructure_code is provided by the Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.