listCollections
AI agents call listCollections to retrieve information from ArangoDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'listCollections' indicates a retrieval operation that enumerates collections in a database. This is a Read operation with no side effects—it queries and returns information only. The low severity reflects minimal blast radius even if called inappropriately. Although the description is empty, the naming pattern and server context strongly support this classification.
From the tool's definition Tool name is 'listCollections' (list operation); no description provided but sibling tools include 'listDatabases' and query tools, establishing pattern that 'list*' operations are Read operations; ArangoDB context confirms this retrieves collection metadata…
Attacks that exploit this kind of access
listCollections. It is categorised as a Read tool in the ArangoDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ArangoDB MCP Server MCP server in PolicyLayer and add a rule for listCollections: 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 ArangoDB MCP Server. Nothing to install.
listCollections 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 listCollections 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 listCollections. 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.
listCollections is provided by the ArangoDB MCP Server MCP server (lucas-deangelis/arango-mcp-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 →