Low Risk

data_summary

Cheap content summary for a ČSÚ dataset from the data layer: number of data cells (pocetUdaju), covered time range (casovaDimenzeOd/Do), per-dimension value counts, and last-change/publish times. Use this before get_data to gauge size, since full datasets can be large. Version (verze) is auto-res...

Part of the Czso Cz server.

data_summary 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 CZSO CZ →

Free to start. No card required.

AI agents call data_summary to retrieve information from Czso Cz 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 data_summary 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": {
    "data_summary": {}
  }
}

See the full Czso Cz policy for all 24 tools.

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

ENFORCE ON MY CZSO CZ →

View all 24 tools →

These attack patterns abuse exactly the kind of access data_summary 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 data_summary only ever does what you allow.

SECURE CZSO CZ →

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

What does the data_summary tool do? +

Cheap content summary for a ČSÚ dataset from the data layer: number of data cells (pocetUdaju), covered time range (casovaDimenzeOd/Do), per-dimension value counts, and last-change/publish times. Use this before get_data to gauge size, since full datasets can be large. Version (verze) is auto-resolved from the catalog if omitted.. It is categorised as a Read tool in the Czso Cz MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on data_summary? +

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

What risk level is data_summary? +

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

Can I rate-limit data_summary? +

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

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

data_summary is provided by the Czso Cz MCP server (https://gateway.pipeworx.io/czso-cz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Czso Cz tool call.

Deterministic rules across all 24 Czso Cz 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.