ListClustersByStatus

Returns a list of Timestream for InfluxDB DB clusters filtered by status (case-insensitive).

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

What ListClustersByStatus does on AWS IoT SiteWise MCP Server

AI agents call ListClustersByStatus to retrieve information from AWS IoT SiteWise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why ListClustersByStatus needs a policy

ListClustersByStatus is a retrieval operation that queries existing cluster metadata without side effects. It matches the Read category pattern of list/get operations. Severity is low because exposing cluster status information has minimal blast radius—an agent could enumerate clusters but cannot modify infrastructure, execute commands, or access sensitive data beyond cluster existence and state.

From the tool's definition Tool returns a filtered list of database clusters by status. The operation is query-based ("returns a list", "filtered by status") with no modification, deletion, or execution of external operations.

Questions about ListClustersByStatus

What does the ListClustersByStatus tool do? +

Returns a list of Timestream for InfluxDB DB clusters filtered by status (case-insensitive). It is categorised as a Read tool in the AWS IoT SiteWise MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ListClustersByStatus? +

Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for ListClustersByStatus: 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 ListClustersByStatus? +

ListClustersByStatus is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ListClustersByStatus? +

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

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

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