cbs_query_dataset
AI agents invoke cbs_query_dataset to trigger actions in Nl Opendata. 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.
The tool name contains 'query' which, combined with the server's mention of DuckDB and data analysis tools, suggests it executes queries (potentially arbitrary SQL via DuckDB) against datasets. This places it in Execute rather than Read. However, the description is empty, lowering confidence. It could range from a simple read/filter to executing arbitrary SQL.
From the tool's definition Tool name 'cbs_query_dataset' and server description mentions 'querying Dutch government open datasets' using 'DuckDB, or Pandas' — querying implies executing queries against data sources.
Attacks that exploit this kind of access
cbs_query_dataset. It is categorised as a Execute tool in the Nl Opendata MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nl Opendata MCP server in PolicyLayer and add a rule for cbs_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 Nl Opendata. Nothing to install.
cbs_query_dataset is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the cbs_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.
Set action: deny in the PolicyLayer policy for cbs_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.
cbs_query_dataset is provided by the Nl Opendata MCP server (soulnai/nl-opendata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →