delete_patient_studies
AI agents call delete_patient_studies to permanently remove resources in Amazon SageMaker AI MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'delete_' prefix combined with 'patient_studies' indicates an irreversible deletion of patient medical data. This is a destructive operation with high blast radius—accidental deletion of patient records could cause serious harm, regulatory violations (HIPAA), and data loss.
From the tool's definition Tool name 'delete_patient_studies' contains 'delete', which is an irreversible operation. The description is empty, limiting direct evidence, but the name strongly indicates permanent removal of medical study data.
Attacks that exploit this kind of access
delete_patient_studies. It is categorised as a Destructive tool in the Amazon SageMaker AI MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Amazon SageMaker AI MCP Server MCP server in PolicyLayer and add a rule for delete_patient_studies: 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 Amazon SageMaker AI MCP Server. Nothing to install.
delete_patient_studies 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_patient_studies 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_patient_studies. 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_patient_studies is provided by the Amazon SageMaker AI MCP Server MCP server (awslabs.sagemaker-ai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.