Lists all keyspaces in the Cassandra/Keyspaces database - args: none
AI agents call listKeyspaces 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.
This tool retrieves and enumerates database schema metadata (keyspaces) without modifying, executing code, or destructively altering any data. It is a straightforward read operation with minimal blast radius—exposure would only leak schema information about the database structure.
From the tool's definition Tool name is 'listKeyspaces' and description states it 'Lists all keyspaces in the Cassandra/Keyspaces database' with no arguments. The verb 'Lists' and action of retrieving keyspace metadata indicates a read-only query operation.
Documented attack patterns abuse exactly the kind of access listKeyspaces gives an agent:
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 listKeyspaces:
{
"version": "1",
"default": "deny",
"tools": {
"listKeyspaces": {}
}
} listKeyspaces is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Lists all keyspaces in the Cassandra/Keyspaces database - args: none. It is categorised as a Read tool in the Amazon Redshift MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amazon Redshift MCP Server MCP server in PolicyLayer and add a rule for listKeyspaces: 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.
listKeyspaces is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the listKeyspaces 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.
Set action: deny in the PolicyLayer policy for listKeyspaces. 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.
listKeyspaces 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.
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.