Revoke a security group egress in the given region
AI agents call revoke-security-group-egress to permanently remove resources in AWS MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Revoking a security group egress rule permanently removes an outbound traffic permission from the security group. This is a destructive, non-reversible action (the rule is deleted), and misuse could disrupt outbound connectivity for all resources associated with that security group, potentially causing widespread service outages. It cannot be undone without knowing and re-adding the exact original rule parameters.
From the tool's definition 'Revoke a security group egress' — revoking a security group rule removes network access controls irreversibly (the rule is deleted and must be manually re-added)
Documented attack patterns abuse exactly the kind of access revoke-security-group-egress gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for revoke-security-group-egress:
{
"version": "1",
"default": "deny",
"hide": [
"revoke-security-group-egress"
]
} revoke-security-group-egress disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Revoke a security group egress in the given region. It is categorised as a Destructive tool in the AWS MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AWS MCP Server MCP server in PolicyLayer and add a rule for revoke-security-group-egress: 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 MCP Server. Nothing to install.
revoke-security-group-egress is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the revoke-security-group-egress 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 revoke-security-group-egress. 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.
revoke-security-group-egress is provided by the AWS MCP Server MCP server (lokeswaran-aj/aws-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS 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.
54 AWS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.