query_cached · Ontario Data MCP: Risk & Policy

WHAT IT DOES

What query_cached does on Ontario Data

AI agents invoke query_cached to trigger actions in Ontario Data. 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_cached needs a policy

The server description mentions 'querying and analyzing datasets' via DuckDB, and the tool name suggests executing queries against cached data. DuckDB supports arbitrary SQL which could include destructive operations. However, with no description available, confidence is reduced.

From the tool's definition Tool name 'query_cached' on a server that uses DuckDB for high-performance analytics; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

query_cached Rate-limited

query_cached 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_cached": {
      "limits": [
        {
          "counter": "query_cached_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 Ontario Data, so you can run agents against it safely.

FAQ

Questions about query_cached

What does the query_cached tool do? +

query_cached. It is categorised as a Execute tool in the Ontario Data 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_cached? +

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

What risk level is query_cached? +

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

Can I rate-limit query_cached? +

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

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

query_cached is provided by the Ontario Data MCP server (sprine/ontario-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

query_cached is one line of Ontario Data's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →