Low Risk

LsInstancesOfCluster

List all Timestream for InfluxDB instances belonging to a specific DB cluster.

How to control LsInstancesOfCluster ↓

What LsInstancesOfCluster does on Amazon Redshift MCP Server

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

Low Risk

Why LsInstancesOfCluster needs a policy

This tool retrieves and lists instances belonging to a database cluster. It has no side effects, does not modify data, execute code, delete resources, or involve financial transactions. It is a straightforward read operation that queries infrastructure state information.

From the tool's definition Tool name 'LsInstancesOfCluster' and description 'List all Timestream for InfluxDB instances' indicate a query/list operation with no modification or execution capability.

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

How to control LsInstancesOfCluster

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "LsInstancesOfCluster": {}
  }
}

LsInstancesOfCluster is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Amazon Redshift 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.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about LsInstancesOfCluster

What does the LsInstancesOfCluster tool do? +

List all Timestream for InfluxDB instances belonging to a specific DB cluster. It is categorised as a Read tool in the Amazon Redshift MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on LsInstancesOfCluster? +

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

What risk level is LsInstancesOfCluster? +

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

Can I rate-limit LsInstancesOfCluster? +

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

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

LsInstancesOfCluster is provided by the Amazon Redshift MCP Server MCP server (awslabs.redshift-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 Redshift MCP Server tool call.

Start from Amazon Redshift 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 Redshift 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.