Low Risk

query_dataset

Query rows from a datos.gov.co dataset using SoQL. datasetId is the Socrata 4x4 code from search_datasets. SoQL clauses: $select (columns / aggregates like "count(*)"), $where (SQL-like filter, e.g. "departamento_nom='BOGOTA' AND edad > 60"), $order ("count desc"), $group, $q (full-text across th...

Part of the Datos Co server.

query_dataset is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE DATOS CO →

Free to start. No card required.

AI agents call query_dataset to retrieve information from Datos Co without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though query_dataset only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

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

See the full Datos Co policy for all 23 tools.

Get this rule live on your own Datos Co server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY DATOS CO →

View all 23 tools →

These attack patterns abuse exactly the kind of access query_dataset gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so query_dataset only ever does what you allow.

SECURE DATOS CO →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the query_dataset tool do? +

Query rows from a datos.gov.co dataset using SoQL. datasetId is the Socrata 4x4 code from search_datasets. SoQL clauses: $select (columns / aggregates like "count(*)"), $where (SQL-like filter, e.g. "departamento_nom='BOGOTA' AND edad > 60"), $order ("count desc"), $group, $q (full-text across the row). Use dataset_columns first to learn field names. Returns an array of row objects keyed by field name. Default $limit is 50 (Socrata max per page is 50000).. It is categorised as a Read tool in the Datos Co MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_dataset? +

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

What risk level is query_dataset? +

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

Can I rate-limit query_dataset? +

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

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

query_dataset is provided by the Datos Co MCP server (https://gateway.pipeworx.io/datos-co/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Datos Co tool call.

Deterministic rules across all 23 Datos Co tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.