oe_collections_sync_db

Refresh collections and memberships from the API into local SQLite. Prunes collections + memberships the server no longer reports.

SERVER: SOURCEhtlin222/openevidence-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade C, identity unverified Pull the record →

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

WHAT IT DOES

What oe_collections_sync_db does on :

AI agents call oe_collections_sync_db to permanently remove resources in :, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why oe_collections_sync_db is rated Critical

The tool irreversibly deletes (prunes) local collections and memberships that are no longer present on the server. While it is a sync/refresh operation, the pruning step is a destructive, non-reversible deletion of local data, making Destructive the most appropriate category.

From the tool's definition Prunes collections + memberships the server no longer reports

Attacks that exploit this kind of access

RECOMMENDED RULE

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

oe_collections_sync_db Hidden

oe_collections_sync_db is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "oe_collections_sync_db"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about oe_collections_sync_db

What does the oe_collections_sync_db tool do? +

Refresh collections and memberships from the API into local SQLite. Prunes collections + memberships the server no longer reports. It is categorised as a Destructive tool in the : MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on oe_collections_sync_db? +

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

oe_collections_sync_db is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit oe_collections_sync_db? +

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

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

oe_collections_sync_db 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 → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →