bak_isos_by_kanton
AI agents call bak_isos_by_kanton 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.
This tool appears to retrieve or query ISOS townscape data filtered by Swiss canton (kanton). It follows the read-only pattern of sibling tools and accesses public cultural heritage information with no side effects. Confidence is slightly reduced due to empty description, but naming convention and context strongly indicate a read operation.
From the tool's definition Tool name 'bak_isos_by_kanton' and sibling tools pattern (bak_list_traditions, bak_isos_statistics, bak_search_isos, bak_get_isos_detail) all indicate data retrieval operations.
Attacks that exploit this kind of access
bak_isos_by_kanton. 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_by_kanton: 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_by_kanton 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_by_kanton 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_by_kanton. 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_by_kanton 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 →