List available database clusters in the specified namespace.
AI agents call list_database_clusters to retrieve information from Mcp Everest without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about existing database clusters without creating, modifying, deleting, or executing operations. It is a straightforward read operation with minimal risk; exposure would allow an AI agent to discover cluster metadata but not alter infrastructure or access sensitive data beyond enumeration.
From the tool's definition Tool name is 'list_database_clusters' and description states 'List available database clusters' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List available database clusters in the specified namespace. It is categorised as a Read tool in the Mcp Everest MCP Server, which means it retrieves data without modifying state.
Register the Mcp Everest MCP server in PolicyLayer and add a rule for list_database_clusters: 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 Everest. Nothing to install.
list_database_clusters 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 list_database_clusters 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 list_database_clusters. 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.
list_database_clusters is provided by the Mcp Everest MCP server (spron-in/mcp-everest). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →