AI agents call get_collections to retrieve information from Archive Agent 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 available Qdrant vector database collections without modifying, executing, or deleting any data. It is a straightforward informational lookup, making it a Read category tool with low severity—misuse would only expose the names/metadata of collections, not cause harm to data or systems.
From the tool's definition Tool name 'get_collections' and description 'Get the list of available Qdrant collections' indicate a retrieval operation with no side effects. The verb 'Get' and the passive retrieval nature confirm read-only access to collection metadata.
Documented attack patterns abuse exactly the kind of access get_collections gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Archive Agent, and nothing reaches the server without passing your rules. This is the rule we recommend for get_collections:
{
"version": "1",
"default": "deny",
"tools": {
"get_collections": {}
}
}get_collections 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.
Get the list of available Qdrant collections. It is categorised as a Read tool in the Archive Agent MCP Server, which means it retrieves data without modifying state.
Register the Archive Agent MCP server in PolicyLayer and add a rule for get_collections: 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 Archive Agent. Nothing to install.
get_collections 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 get_collections 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 get_collections. 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.
get_collections is provided by the Archive Agent MCP server (shredengineer/archive-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Archive Agent tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 Archive Agent tools catalogued and risk-classified — across an index of 42,500+ MCP servers.