select-database · Ravendb MCP: Risk & Policy

WHAT IT DOES

What select-database does on Ravendb

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

WHY IT NEEDS A POLICY

Why select-database needs a policy

Switching the active database context modifies the session/connection state, which is a reversible state change (you can switch back). It does not retrieve data (Read) nor delete anything (Destructive), but it does alter the operational context, qualifying as Write.

From the tool's definition 'Switch to a specific database context' — changes the active database context for subsequent operations

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

select-database Rate-limited

select-database 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": {
    "select-database": {
      "limits": [
        {
          "counter": "select-database_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ravendb, so you can run agents against it safely.

FAQ

Questions about select-database

What does the select-database tool do? +

Switch to a specific database context. It is categorised as a Write tool in the Ravendb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on select-database? +

Register the Ravendb MCP server in PolicyLayer and add a rule for select-database: 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 Ravendb. Nothing to install.

What risk level is select-database? +

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

Can I rate-limit select-database? +

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

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

select-database is provided by the Ravendb MCP server (johnib/ravendb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.