oe_collections_list
List all collections owned by the authenticated user.
This record as markdown: /tools/htlin222-openevidence-mcp/oe-collections-list.md
What oe_collections_list does on :
AI agents call oe_collections_list to retrieve information from : without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why oe_collections_list is rated Low
This tool queries and returns existing data (collections) belonging to the user. It performs no modifications, deletions, or external operations. The scope is limited to the authenticated user's own data, minimizing blast radius. Classification as Read with low severity is appropriate.
From the tool's definition Tool description states 'List all collections owned by the authenticated user.' The verb 'list' indicates a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs oe_collections_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and :, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For oe_collections_list, this is the rule to start with:
oe_collections_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect :, apply this rule, and every oe_collections_list call is checked against it from then on.
Questions about oe_collections_list
List all collections owned by the authenticated user. It is categorised as a Read tool in the : MCP Server, which means it retrieves data without modifying state.
Register the : MCP server in PolicyLayer and add a rule for oe_collections_list: 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 :. Nothing to install.
oe_collections_list 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 oe_collections_list 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 oe_collections_list. 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.
oe_collections_list is provided by the : MCP server (htlin222/openevidence-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on :, and thousands of servers like it.
This server
Across the catalogue