Fetch a single Wanderland route by its feature id (as returned by list_named_routes). Returns attributes (name, number, category, length) and the full geometry (LineString or MultiLineString).
AI agents call get_named_route to retrieve information from Bergauf without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves hiking route information by ID, including metadata and geometric data. It performs a read-only query operation with no capability to modify, delete, or execute external operations. The data returned is static route information used for planning purposes. No side effects or irreversible actions are possible.
From the tool's definition Tool description states 'Fetch a single Wanderland route' and 'Returns attributes (name, number, category, length) and the full geometry'. The verb 'fetch' and 'returns' indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_named_route gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bergauf, and nothing reaches the server without passing your rules. This is the rule we recommend for get_named_route:
{
"version": "1",
"default": "deny",
"tools": {
"get_named_route": {}
}
}get_named_route is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch a single Wanderland route by its feature id (as returned by list_named_routes). Returns attributes (name, number, category, length) and the full geometry (LineString or MultiLineString). It is categorised as a Read tool in the Bergauf MCP Server, which means it retrieves data without modifying state.
Register the Bergauf MCP server in PolicyLayer and add a rule for get_named_route: 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 Bergauf. Nothing to install.
get_named_route 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 get_named_route 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 get_named_route. 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.
get_named_route is provided by the Bergauf MCP server (lailo/bergauf). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bergauf, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Bergauf tools catalogued and risk-classified — across an index of 43,000+ MCP servers.