query_registered_database · MelviChat MCP Server MCP

WHAT IT DOES

What query_registered_database does on MelviChat MCP Server

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

This tool executes arbitrary SQL queries directly against a registered database. While named 'query', the ability to run direct SQL means it could execute DML or DDL statements (INSERT, UPDATE, DELETE, DROP), not just SELECTs. The most severe applicable category is Execute (potentially Destructive depending on what SQL is permitted).

From the tool's definition "Ejecutar una consulta SQL directa en una base de datos registrada" — 'Ejecutar' means 'Execute' and 'consulta SQL directa' means 'direct SQL query'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

query_registered_database Rate-limited

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

FAQ

Questions about query_registered_database

What does the query_registered_database tool do? +

Ejecutar una consulta SQL directa en una base de datos registrada. It is categorised as a Execute tool in the MelviChat 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 query_registered_database? +

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

What risk level is query_registered_database? +

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

Can I rate-limit query_registered_database? +

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

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

query_registered_database is provided by the MelviChat MCP Server MCP server (melvi24/mcp-chat-ia). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.