This record as markdown: /tools/aws/delete-study.md
What delete_study does on AWS
AI agents call delete_study to permanently remove resources in AWS, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_study is rated Critical
The tool name explicitly indicates deletion ('delete_study'). Deletion is an irreversible operation that cannot be undone. While confidence is slightly reduced due to lack of a description confirming the scope and nature of the study resource being deleted, the verb 'delete' itself is unambiguous enough to classify this as Destructive.
From the tool's definition Tool name is 'delete_study' which contains the verb 'delete' indicating irreversible data removal. No description provided, but the semantic meaning of 'delete' combined with AWS context suggests permanent deletion of a study resource.
Attacks that exploit this kind of access
The rule that runs delete_study 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 delete_study, this is the rule to start with:
delete_study is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AWS, apply this rule, and every delete_study call is checked against it from then on.
Questions about delete_study
delete_study is a destructive tool on the AWS MCP server. It is categorised as a Destructive tool in the AWS MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AWS MCP server in PolicyLayer and add a rule for delete_study: 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.
delete_study 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_study 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_study. 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_study 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.
Across the catalogue