Low Risk

query

Low-level compatibility tool. Execute a read-only MongoDB query envelope with { collection, operation, filter?, pipeline?, field?, limit? }. Prefer the dedicated find, aggregate, count, and distinct tools when possible.

How to control query ↓

What query does on Askdb

AI agents call query to retrieve information from Askdb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why query needs a policy

The tool is documented as read-only, executing MongoDB queries (find, aggregate, count, distinct operations) without side effects. Severity is medium rather than low because it accepts a low-level query envelope with arbitrary filter and pipeline parameters, which could expose sensitive data across any collection if field-level controls are misconfigured or bypassed.

From the tool's definition 'Execute a read-only MongoDB query envelope' and 'Prefer the dedicated find, aggregate, count, and distinct tools when possible' — explicitly described as read-only

Documented attack patterns abuse exactly the kind of access query gives an agent:

How to control query

PolicyLayer is an MCP gateway — it sits between your AI agents and Askdb, and nothing reaches the server without passing your rules. This is the rule we recommend for query:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "query": {}
  }
}

query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Askdb — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about query

What does the query tool do? +

Low-level compatibility tool. Execute a read-only MongoDB query envelope with { collection, operation, filter?, pipeline?, field?, limit? }. Prefer the dedicated find, aggregate, count, and distinct tools when possible. It is categorised as a Read tool in the Askdb MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query? +

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

What risk level is query? +

query is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit query? +

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

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

query is provided by the Askdb MCP server (mgorabbani/askdb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Askdb tool call.

Start from Askdb, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

10 Askdb tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.