data.query · Kelnix Datamind Curator MCP: Risk & Policy

WHAT IT DOES

What data.query does on Kelnix Datamind Curator

AI agents invoke data.query to trigger actions in Kelnix Datamind Curator. 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 data.query needs a policy

The server description explicitly mentions 'query with natural language' as a core capability. A query tool that executes natural language or SQL-like queries against arbitrary connected data sources is most accurately classified as Execute, since the effects depend heavily on arguments and may include arbitrary data retrieval or manipulation. Because the description is empty, confidence is lowered.

From the tool's definition Tool name is 'data.query' on a server that supports 'natural language' queries against connected data sources; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

data.query Rate-limited

data.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": {
    "data.query": {
      "limits": [
        {
          "counter": "data.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 Kelnix Datamind Curator, so you can run agents against it safely.

FAQ

Questions about data.query

What does the data.query tool do? +

data.query. It is categorised as a Execute tool in the Kelnix Datamind Curator MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on data.query? +

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

What risk level is data.query? +

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

Can I rate-limit data.query? +

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

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

data.query is provided by the Kelnix Datamind Curator MCP server (kelnixsolutions/kelnix-datamind-curator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.