oe_collections_db_init

Create the local SQLite mirror at $OE_MCP_DB_PATH (default ~/.openevidence-mcp/db/oe.sqlite). Idempotent.

SERVER: SOURCEhtlin222/openevidence-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade C, identity unverified Pull the record →

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

WHAT IT DOES

What oe_collections_db_init does on :

AI agents use oe_collections_db_init to create or update resources in :, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your : environment.

RISK

Why oe_collections_db_init is rated Medium

This tool creates/initializes a local SQLite database file. While creation is reversible (the file can be deleted), it modifies the local filesystem state and establishes persistent data storage. This qualifies as Write rather than Destructive because initialization is not inherently destructive, and it's marked idempotent (safe to re-run).

From the tool's definition Tool description states 'Create the local SQLite mirror' and 'Idempotent', indicating it creates or initializes a database file.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

oe_collections_db_init Rate-limited

oe_collections_db_init stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "oe_collections_db_init": {
      "limits": [
        {
          "counter": "oe_collections_db_init_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about oe_collections_db_init

What does the oe_collections_db_init tool do? +

Create the local SQLite mirror at $OE_MCP_DB_PATH (default ~/.openevidence-mcp/db/oe.sqlite). Idempotent. It is categorised as a Write tool in the : MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on oe_collections_db_init? +

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

oe_collections_db_init is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit oe_collections_db_init? +

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

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

oe_collections_db_init 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

Govern customer-ops agents →Argument validation →Scoped token →