AI agents call delete_role_policy to permanently remove resources in AWS Lambda Tool MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting IAM role policies is a destructive operation that irreversibly removes permissions and cannot be easily undone. While not directly causing data loss, it removes security configurations that could lock out users or services from critical resources. This warrants 'Destructive' classification with high severity due to potential operational impact and difficulty of recovery without proper audit trails.
From the tool's definition Tool name 'delete_role_policy' explicitly indicates deletion of AWS IAM role policies. The verb 'delete' indicates irreversible removal of access control configurations.
Documented attack patterns abuse exactly the kind of access delete_role_policy gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Lambda Tool MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_role_policy:
{
"version": "1",
"default": "deny",
"hide": [
"delete_role_policy"
]
}delete_role_policy 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.
delete_role_policy. It is categorised as a Destructive tool in the AWS Lambda Tool MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AWS Lambda Tool MCP Server MCP server in PolicyLayer and add a rule for delete_role_policy: 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 Lambda Tool MCP Server. Nothing to install.
delete_role_policy 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 delete_role_policy 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 delete_role_policy. 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.
delete_role_policy is provided by the AWS Lambda Tool MCP Server MCP server (awslabs.lambda-tool-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS Lambda Tool 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 Lambda Tool MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.