swisstopo_find_features
AI agents call swisstopo_find_features to retrieve information from Pypi:swisstopo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'find_features' combined with the server's read-only geodata API context (maps, elevation, geocoding) strongly suggests this retrieves or searches geographic features without modification. Despite empty description, confidence is moderate (0.75) due to consistent naming pattern with sibling tools and server purpose.
From the tool's definition Tool name 'swisstopo_find_features' and server context indicate feature querying/search capability. Sibling tools (swisstopo_get_feature, swisstopo_identify_features) and server description ('maps, elevation, geocoding, cadastral extracts') confirm this is a…
Attacks that exploit this kind of access
swisstopo_find_features. It is categorised as a Read tool in the Pypi:swisstopo MCP Server, which means it retrieves data without modifying state.
Register the Pypi:swisstopo MCP server in PolicyLayer and add a rule for swisstopo_find_features: 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:swisstopo. Nothing to install.
swisstopo_find_features 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 swisstopo_find_features 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 swisstopo_find_features. 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.
swisstopo_find_features is provided by the Pypi:swisstopo MCP server (malkreide/swisstopo-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 →