delete

THE RISK

Critical Risk

Why delete needs a policy

The tool name 'delete' combined with the AWS/business context indicates an operation that removes data without a reversible mechanism. Without a description to confirm scope, we must classify conservatively at the highest risk level. The blast radius is critical: an agent invoking 'delete' with incorrect parameters could permanently remove business-critical data (cases, attachments, policies, or user configurations).

From the tool's definition Tool named 'delete' with no description provided. Given the context of an AWS Labs MCP server for Amazon Q Business with sibling tools that include case/attachment/policy management operations, a 'delete' tool almost certainly performs irreversible data…

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

POLICY

How to control delete

PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Labs amazon-qindex MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete"
  ]
}

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

Create a free account and register AWS Labs amazon-qindex MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More AWS Labs amazon-qindex MCP Server tools

Destructive bulk_delete_by_criteria bulk_delete_by_criteria Destructive cache_delete Delete a value from the cache. Destructive cache_delete_many Delete multiple values from the cache. Destructive cache_delete_multi Delete multiple values from the cache (alias for delete_many). Destructive delete_access_key delete_access_key Destructive delete_agent_runtime delete_agent_runtime Destructive delete_agent_runtime_endpoint delete_agent_runtime_endpoint Destructive delete_app delete_app

All 805 AWS Labs amazon-qindex MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in AWS Labs amazon-qindex MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete

What does the delete tool do? +

delete. It is categorised as a Destructive tool in the AWS Labs amazon-qindex 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? +

Register the AWS Labs amazon-qindex MCP Server MCP server in PolicyLayer and add a rule for delete: 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 Labs amazon-qindex MCP Server. Nothing to install.

What risk level is delete? +

delete 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? +

Yes. Add a rate_limit block to the delete 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 completely? +

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

delete is provided by the AWS Labs amazon-qindex MCP Server MCP server (awslabs.amazon-qindex-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 AWS Labs amazon-qindex MCP Server tool call.

Start from AWS Labs amazon-qindex MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →