stream_group_delete_consumer

Delete consumer from group.

Server AWS IoT SiteWise MCP Server awslabs.aws-iot-sitewise-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What stream_group_delete_consumer does on AWS IoT SiteWise MCP Server

AI agents call stream_group_delete_consumer to permanently remove resources in AWS IoT SiteWise MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why stream_group_delete_consumer needs a policy

Deletion is inherently destructive and cannot be undone without external recovery mechanisms. While the blast radius is limited to a single consumer entity (not system-wide), removing a consumer from a group can disrupt dependent processes and break application logic. This is more severe than Write operations but less critical than cascading deletions, warranting 'high' severity.

From the tool's definition Tool name 'stream_group_delete_consumer' explicitly performs deletion ('delete') with no indication of reversibility. The description states 'Delete consumer from group,' which is an irreversible operation that removes an entity from a stream group.

Questions about stream_group_delete_consumer

What does the stream_group_delete_consumer tool do? +

Delete consumer from group. It is categorised as a Destructive tool in the AWS IoT SiteWise 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_group_delete_consumer? +

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

What risk level is stream_group_delete_consumer? +

stream_group_delete_consumer 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_group_delete_consumer? +

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

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

stream_group_delete_consumer is provided by the AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.