This record as markdown: /tools/aws/generate-infrastructure-code.md
What generate_infrastructure_code does on AWS
AI agents invoke generate_infrastructure_code to trigger actions in AWS. 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 generate_infrastructure_code is rated High
The name suggests generating infrastructure code (e.g., CloudFormation, Terraform, CDK), which at minimum is a Write operation producing code artifacts, but could also involve executing or deploying infrastructure changes. Given the AWS context and sibling tools that include policy attachment and audit operations, this tool likely produces code that could trigger infrastructure provisioning.
From the tool's definition Tool name 'generate_infrastructure_code' — description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs generate_infrastructure_code safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AWS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For generate_infrastructure_code, this is the rule to start with:
generate_infrastructure_code 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.
The button opens the PolicyLayer dashboard: create your workspace, connect AWS, apply this rule, and every generate_infrastructure_code call is checked against it from then on.
Questions about generate_infrastructure_code
generate_infrastructure_code is a execute tool on the AWS MCP server. It is categorised as a Execute tool in the AWS MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AWS 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 AWS. Nothing to install.
generate_infrastructure_code 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 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.
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.
generate_infrastructure_code is provided by the AWS MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AWS, and thousands of servers like it.
This server
Across the catalogue