readWriteQuery · ArangoDB MCP Server MCP: Risk & Policy

WHAT IT DOES

What readWriteQuery does on ArangoDB MCP Server

AI agents invoke readWriteQuery to trigger actions in ArangoDB MCP Server. 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 readWriteQuery needs a policy

The name 'readWriteQuery' suggests it can execute queries that both read and modify data. With no description to narrow scope, the most severe applicable category given 'write' in the name is Write, but since it executes arbitrary queries (analogous to sibling 'readQuery' which runs queries), it falls under Execute.

From the tool's definition Tool name 'readWriteQuery' implies both read and write operations; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

readWriteQuery Rate-limited

readWriteQuery 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": {
    "readWriteQuery": {
      "limits": [
        {
          "counter": "readwritequery_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 ArangoDB MCP Server, so you can run agents against it safely.

FAQ

Questions about readWriteQuery

What does the readWriteQuery tool do? +

readWriteQuery. It is categorised as a Execute tool in the ArangoDB MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on readWriteQuery? +

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

What risk level is readWriteQuery? +

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

Can I rate-limit readWriteQuery? +

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

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

readWriteQuery is provided by the ArangoDB MCP Server MCP server (lucas-deangelis/arango-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.