Estimates the size of a dataset before fetching.
AI agents call cbs_estimate_dataset_size to retrieve information from Nl Opendata without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves or computes metadata about dataset size to inform the user before a fetch operation. It has no side effects on the data itself, performs no destructive actions, executes no arbitrary code, and involves no financial transactions. It is a straightforward Read operation analogous to checking file properties.
From the tool's definition Tool name 'cbs_estimate_dataset_size' and description 'Estimates the size of a dataset before fetching' indicate a query/inspection operation that retrieves metadata without modifying, deleting, or executing arbitrary code.
Attacks that exploit this kind of access
Estimates the size of a dataset before fetching. It is categorised as a Read tool in the Nl Opendata MCP Server, which means it retrieves data without modifying state.
Register the Nl Opendata MCP server in PolicyLayer and add a rule for cbs_estimate_dataset_size: 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_estimate_dataset_size is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cbs_estimate_dataset_size 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_estimate_dataset_size. 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_estimate_dataset_size 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 →