query-documents · Ravendb MCP: Risk & Policy

WHAT IT DOES

What query-documents does on Ravendb

AI agents invoke query-documents to trigger actions in Ravendb. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why query-documents needs a policy

Executing arbitrary RQL queries can encompass read operations, but RQL also supports update and patch operations (e.g., UPDATE clauses). The tool's blast radius is high because a malicious or erroneous query could modify or expose large amounts of data. Since the description says 'Execute RQL queries' without restricting to SELECT-only, the most severe applicable category is Execute.

From the tool's definition "Execute RQL queries" — the tool runs arbitrary RQL (RavenDB Query Language) queries against the database, whose effects depend entirely on the query arguments supplied.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

query-documents Rate-limited

query-documents stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "query-documents": {
      "limits": [
        {
          "counter": "query-documents_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 query-documents

What does the query-documents tool do? +

Execute RQL queries with results handling. It is categorised as a Execute tool in the Ravendb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on query-documents? +

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

query-documents is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit query-documents? +

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

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

query-documents 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.