Critical Risk →

stream_delete

Delete entries from stream.

How to control stream_delete ↓

What stream_delete does on Amazon Data Processing MCP Server

AI agents call stream_delete 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 stream_delete needs a policy

Deleting entries from a stream is an irreversible operation that destroys data and cannot be undone. This meets the definition of Destructive category. Severity is high because stream deletion could affect data pipelines, analytics, and dependent systems, though the blast radius depends on stream size and criticality. Confidence is high based on explicit use of 'delete' terminology.

From the tool's definition Tool name is 'stream_delete' and description states 'Delete entries from stream.' The verb 'delete' combined with the action of removing entries indicates irreversible data removal.

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

How to control stream_delete

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

  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 stream_delete

What does the stream_delete tool do? +

Delete entries from stream. 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 stream_delete? +

Register the Amazon Data Processing MCP Server 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 Amazon Data Processing MCP Server. 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 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.