db_query · Overlord MCP Server MCP: Risk & Policy

WHAT IT DOES

What db_query does on Overlord MCP Server

AI agents invoke db_query to trigger actions in Overlord 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 db_query needs a policy

A 'db_query' tool on a C2 framework server likely executes arbitrary SQL queries against the database. Given the context of the server (Overlord C2 framework managing clients, builds, users, audit logs), arbitrary SQL execution could allow reading sensitive data, modifying records, or issuing destructive DDL/DML statements.

From the tool's definition Tool name 'db_query' on a C2 framework server with sibling tools like 'delete_build_profile', 'delete_client', 'delete_offline_clients' suggesting broad destructive capabilities; description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

db_query Rate-limited

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

FAQ

Questions about db_query

What does the db_query tool do? +

db_query. It is categorised as a Execute tool in the Overlord 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 db_query? +

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

What risk level is db_query? +

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

Can I rate-limit db_query? +

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

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

db_query is provided by the Overlord MCP Server MCP server (skeeminator/overlord-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.