Critical Risk →

delete_datastore

Delete a data store from AWS HealthImaging.

How to control delete_datastore ↓

What delete_datastore does on Amazon Data Processing MCP Server

AI agents call delete_datastore to permanently remove resources in Amazon Data Processing MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_datastore needs a policy

This tool permanently removes a datastore, which cannot be undone. Data loss is irreversible. While not financial, the destructive nature and potential blast radius of accidentally deleting a medical imaging datastore (given HealthImaging context) warrants 'high' severity. Confidence is high due to explicit 'delete' action on persistent storage.

From the tool's definition Tool name 'delete_datastore' combined with description 'Delete a data store from AWS HealthImaging' explicitly indicates irreversible deletion of data storage resources.

Documented attack patterns abuse exactly the kind of access delete_datastore gives an agent:

How to control delete_datastore

PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Data Processing MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_datastore:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_datastore"
  ]
}

delete_datastore disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Amazon Data Processing MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_datastore

What does the delete_datastore tool do? +

Delete a data store from AWS HealthImaging. It is categorised as a Destructive tool in the Amazon Data Processing MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_datastore? +

Register the Amazon Data Processing MCP Server MCP server in PolicyLayer and add a rule for delete_datastore: 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 Data Processing MCP Server. Nothing to install.

What risk level is delete_datastore? +

delete_datastore is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_datastore? +

Yes. Add a rate_limit block to the delete_datastore 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.

How do I block delete_datastore completely? +

Set action: deny in the PolicyLayer policy for delete_datastore. 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.

What MCP server provides delete_datastore? +

delete_datastore is provided by the Amazon Data Processing MCP Server MCP server (awslabs.aws-dataprocessing-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Amazon Data Processing MCP Server tool call.

Start from Amazon Data Processing 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 Amazon Data Processing MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.