getCollections
AI agents call getCollections to retrieve information from MCP Database Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves structural information about available database collections. It has no side effects and cannot modify, delete, or execute operations. The empty description reduces confidence slightly, but the tool name and server context make the read classification clear. Severity is low because listing collections poses minimal risk—it reveals schema information but not sensitive data values.
From the tool's definition Tool name 'getCollections' indicates retrieval of collection metadata. Server description lists 'querying' as a read operation; getCollections is a list/fetch operation that returns available collections without modifying data.
Attacks that exploit this kind of access
getCollections. It is categorised as a Read tool in the MCP Database Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Database Server MCP server in PolicyLayer and add a rule for getCollections: 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 Database Server. Nothing to install.
getCollections 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 getCollections 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 getCollections. 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.
getCollections is provided by the MCP Database Server MCP server (manpreet2000/mcp-database-server). 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 →