database_query · MCP Workspace Server MCP: Risk & Policy

WHAT IT DOES

What database_query does on MCP Workspace Server

AI agents invoke database_query to trigger actions in MCP Workspace 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 database_query needs a policy

This tool executes arbitrary SQL queries, which can include not just SELECT statements but also INSERT, UPDATE, DELETE, DROP, and other DDL/DML operations. Since it permits arbitrary SQL execution, it spans from Read all the way to Destructive. Per the rules, the most severe applicable category is chosen.

From the tool's definition 'Execute SQL queries on SQLite databases within the workspace'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

database_query Rate-limited

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

FAQ

Questions about database_query

What does the database_query tool do? +

Execute SQL queries on SQLite databases within the workspace. It is categorised as a Execute tool in the MCP Workspace 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 database_query? +

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

What risk level is database_query? +

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

Can I rate-limit database_query? +

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

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

database_query is provided by the MCP Workspace Server MCP server (shayyeffet/ultimate_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.