oe_collections_summary

Counts (chats, collections, hashtag, memberships, unsorted) + last sync timestamps.

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-summary.md

WHAT IT DOES

What oe_collections_summary does on :

AI agents call oe_collections_summary 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_summary is rated Low

This tool performs read-only queries to count and retrieve metadata about collections and related entities. It has no side effects, creates no data, executes no code, and makes no destructive or financial operations. It is a simple retrieval/reporting function with minimal blast radius if misused.

From the tool's definition Tool description states it 'Counts (chats, collections, hashtag, memberships, unsorted) + last sync timestamps' — retrieves aggregated statistics and metadata without modifying any data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

oe_collections_summary Allowed

oe_collections_summary 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_summary": {}
  }
}

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_summary call is checked against it from then on.

FAQ

Questions about oe_collections_summary

What does the oe_collections_summary tool do? +

Counts (chats, collections, hashtag, memberships, unsorted) + last sync timestamps. 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_summary? +

Register the : MCP server in PolicyLayer and add a rule for oe_collections_summary: 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_summary? +

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

Can I rate-limit oe_collections_summary? +

Yes. Add a rate_limit block to the oe_collections_summary 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_summary completely? +

Set action: deny in the PolicyLayer policy for oe_collections_summary. 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_summary? +

oe_collections_summary 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

The MCP Attack Database →

Guides

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