stream_delete

THE RISK

Critical Risk

Why stream_delete needs a policy

Deletion of stream entries is an irreversible operation that cannot be undone. Even though the blast radius is somewhat constrained by requiring both a key and id parameter, unauthorized or mistaken deletion of stream data could cause data loss. This qualifies as Destructive rather than Write because the operation is permanent and removes data rather than modifying it reversibly.

From the tool's definition Tool name is 'stream_delete' and description explicitly states 'Delete entries from stream.' The function parameters include 'key' and 'id' to identify which entries to delete. The return is a success or error message, confirming deletion was attempted.

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

POLICY

How to control stream_delete

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

policy.json

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

stream_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 — 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 tools

Destructive bulk_delete_by_criteria bulk_delete_by_criteria Destructive cache_delete Delete a value from the cache. Args: key: The key to delete Returns: Destructive cache_delete_many Delete multiple values from the cache. Args: keys: List of keys to delete Destructive cache_delete_multi Delete multiple values from the cache (alias for delete_many). Args: keys: Li Destructive delete Delete a Valkey key. Args: key (str): The key to delete. Returns: Destructive delete_access_key delete_access_key Destructive delete_datastore Delete a data store from AWS HealthImaging. Destructive delete_group delete_group

All 300 AWS 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

Govern infrastructure agents → Production lockdown, region locks, and approval-to-delete on every infrastructure call agents make.
Critical-risk tools in AWS → 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 →
PolicyLayer vs alternatives → How deterministic, per-call MCP policy compares with gateways, identity layers, and authorisation platforms.

FAQ

Questions about stream_delete

What does the stream_delete tool do? +

Delete entries from stream. Args: key: The name of the key id: Entry ID to delete Returns: Success message or error message. 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.

How do I enforce a policy on stream_delete? +

Register the AWS MCP server in PolicyLayer and add a rule for stream_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. Nothing to install.

What risk level is stream_delete? +

stream_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 stream_delete? +

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

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

stream_delete 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.

Enforce policy on every AWS tool call.

Start from AWS, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →