confirm_query · QueryNest MCP: Risk & Policy

WHAT IT DOES

What confirm_query does on QueryNest

AI agents invoke confirm_query to trigger actions in QueryNest. 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 confirm_query needs a policy

This tool executes MongoDB queries against live database instances. While its primary use is read-oriented queries, MongoDB queries can include aggregation pipelines, updates, or other operations depending on what was 'generated'. The tool runs arbitrary generated queries, which could have broad effects.

From the tool's definition 执行生成的MongoDB查询并返回结果 — '执行' means 'execute'; the tool runs a generated MongoDB query and returns results

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

confirm_query Rate-limited

confirm_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": {
    "confirm_query": {
      "limits": [
        {
          "counter": "confirm_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 QueryNest, so you can run agents against it safely.

FAQ

Questions about confirm_query

What does the confirm_query tool do? +

执行生成的MongoDB查询并返回结果. It is categorised as a Execute tool in the QueryNest MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on confirm_query? +

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

What risk level is confirm_query? +

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

Can I rate-limit confirm_query? +

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

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

confirm_query is provided by the QueryNest MCP server (niuzaishu/querynest). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.