New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_stream

Deletes a stream, specified by the provided resource 'name' parameter. * The resource 'name' parameter is in the form: 'projects/{project name}/locations/{location}/streams/{stream name}', for example: 'projects/my-project/locations/us-central1/streams/my-streams'. * This tool returns a long-runn...

SERVERMcp SOURCEhttps://datastream.googleapis.com/mcp
Critical RISK CLASS
Category Destructive
Parameters 21 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-googleapis-datastream-mcp/delete-stream.md

What delete_stream does on Mcp

AI agents call delete_stream to permanently remove resources in Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

ParameterTypeRequiredDescription
name string Yes Required. The name of the stream resource to delete.
requestId string Optional. A request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if i

Parameters from the server's own tool schema.

Why delete_stream is rated Critical

This tool permanently deletes a stream resource from Google Cloud Datastream. Deletion operations are inherently irreversible and destructive. The high severity reflects the blast radius: an AI agent with misuse could delete production data pipelines, interrupting critical data replication workflows. The confidence is high because the intent is unambiguous from both the name and description.

From the tool's definition Tool name is 'delete_stream' and description states 'Deletes a stream' with no reversibility mentioned. The operation removes a Google Cloud Datastream resource by name, which is an irreversible action that cannot be undone.

Risk signalsBulk/mass operation — affects multiple targets

Questions about delete_stream

What does the delete_stream tool do? +

Deletes a stream, specified by the provided resource 'name' parameter. * The resource 'name' parameter is in the form: 'projects/{project name}/locations/{location}/streams/{stream name}', for example: 'projects/my-project/locations/us-central1/streams/my-streams'. * This tool returns a long-running operation. Use the 'get_operation' tool with the returned operation name to poll its status until it completes. Operation may take several minutes; do not check more often than every ten seconds. It is categorised as a Destructive tool in the Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does delete_stream accept? +

delete_stream accepts 2 parameters: name, requestId. Required: name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on delete_stream? +

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

What risk level is delete_stream? +

delete_stream 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_stream? +

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

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

delete_stream is provided by the MCP server (https://datastream.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on , and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.