query_database · MCP-Maker MCP: Risk & Policy

WHAT IT DOES

What query_database does on MCP-Maker

AI agents invoke query_database to trigger actions in MCP-Maker. 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_database needs a policy

The tool name 'query_database' suggests execution of database queries. Given the server auto-generates MCP servers from arbitrary data sources and enables querying with zero code, this tool likely executes arbitrary or semi-arbitrary SQL/query language against a database. This could range from read-only SELECT to destructive DROP/DELETE depending on implementation.

From the tool's definition Tool name 'query_database' on a server described as enabling AI clients to 'query databases, spreadsheets, and APIs with zero code'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

query_database Rate-limited

query_database 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_database": {
      "limits": [
        {
          "counter": "query_database_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-Maker, so you can run agents against it safely.

FAQ

Questions about query_database

What does the query_database tool do? +

query_database. It is categorised as a Execute tool in the MCP-Maker 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_database? +

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

What risk level is query_database? +

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

Can I rate-limit query_database? +

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

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

query_database is provided by the MCP-Maker MCP server (mralihasan/mcp-maker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.