bak_isos_statistics
AI agents call bak_isos_statistics to retrieve information from Pypi:swiss Culture without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to compute or retrieve statistics about ISOS (Inventaire Suisse des Sites d'importance nationale) townscapes. Given the server's purpose (providing access to cultural heritage data with no API key required) and sibling tools that are all queries or list operations (bak_get_*, bak_list_*, bak_search_*), this is almost certainly a Read operation that returns aggregated or computed data without…
From the tool's definition Tool name 'bak_isos_statistics' suggests aggregation/reporting on ISOS townscape data; no description provided but naming pattern and context within a read-only cultural heritage data server indicate data retrieval.
Attacks that exploit this kind of access
bak_isos_statistics. It is categorised as a Read tool in the Pypi:swiss Culture MCP Server, which means it retrieves data without modifying state.
Register the Pypi:swiss Culture MCP server in PolicyLayer and add a rule for bak_isos_statistics: 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 Pypi:swiss Culture. Nothing to install.
bak_isos_statistics 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 bak_isos_statistics 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 bak_isos_statistics. 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.
bak_isos_statistics is provided by the Pypi:swiss Culture MCP server (malkreide/swiss-culture-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 →