AI agents invoke policy_generation_start to trigger actions in AWS Support MCP Server. 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.
Policy generation is an autonomous operation that creates or modifies AWS IAM configurations. It does not merely read data (would be Read), nor is it inherently destructive in the sense of deletion. However, it executes a process that modifies AWS security posture. The empty description reduces confidence slightly, but the name and context clearly indicate an Execute action rather than Read or Write.
From the tool's definition Tool name 'policy_generation_start' suggests initiating a policy generation process. The AWS Support MCP server context and sibling tools like 'add_inline_policy' and 'add_user_to_group' indicate this operates on AWS IAM policies.
Documented attack patterns abuse exactly the kind of access policy_generation_start gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Support MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for policy_generation_start:
{
"version": "1",
"default": "deny",
"tools": {
"policy_generation_start": {
"limits": [
{
"counter": "policy_generation_start_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}policy_generation_start 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.
Free to start. No card required.
policy_generation_start. It is categorised as a Execute tool in the AWS Support MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AWS Support MCP Server MCP server in PolicyLayer and add a rule for policy_generation_start: 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 Support MCP Server. Nothing to install.
policy_generation_start 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 policy_generation_start 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 policy_generation_start. 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.
policy_generation_start is provided by the AWS Support MCP Server MCP server (awslabs.aws-support-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS Support MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 AWS Support MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.