oe_collections_get

Fetch a collection (incl. nested questions[] = membership list) by id.

SERVER: SOURCEhtlin222/openevidence-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/htlin222-openevidence-mcp/oe-collections-get.md

WHAT IT DOES

What oe_collections_get does on :

AI agents call oe_collections_get 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.

RISK

Why oe_collections_get is rated Low

The tool retrieves collection data by id and returns nested membership information. The verb 'Fetch' and the read-only nature of querying collection metadata and membership lists places this squarely in the Read category. No data is created, modified, deleted, or executed. Severity is low because retrieving collection metadata poses minimal risk even if misused by an agent.

From the tool's definition Tool description states 'Fetch a collection' and 'membership list' — pure data retrieval with no modifications or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs oe_collections_get 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_get, this is the rule to start with:

oe_collections_get Allowed

oe_collections_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "oe_collections_get": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect :, apply this rule, and every oe_collections_get call is checked against it from then on.

FAQ

Questions about oe_collections_get

What does the oe_collections_get tool do? +

Fetch a collection (incl. nested questions[] = membership list) by id. It is categorised as a Read tool in the : MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on oe_collections_get? +

Register the : MCP server in PolicyLayer and add a rule for oe_collections_get: 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.

What risk level is oe_collections_get? +

oe_collections_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit oe_collections_get? +

Yes. Add a rate_limit block to the oe_collections_get 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.

How do I block oe_collections_get completely? +

Set action: deny in the PolicyLayer policy for oe_collections_get. 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.

What MCP server provides oe_collections_get? +

oe_collections_get 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.

KEEP EXPLORING

More on :, and thousands of servers like it.

This server

All 19 : tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →