Given a WGS84 GeoJSON LineString (usually the geometry from get_named_route), return distance, ascent, descent, max/min elevation, elevation samples, and an estimated walking time using the SAC/DAV formula.
AI agents call get_hike_profile 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.
get_hike_profile takes a GeoJSON LineString as input and computes derived metrics (distance, elevation profile, walking time estimates) from that geometry. This is a pure data analysis operation—no creation, modification, deletion, or execution of external commands. The tool has no side effects and only produces informational output to support hiking planning. It falls squarely into the Read category.
From the tool's definition Tool description states it returns analysis of provided hiking route data: 'return distance, ascent, descent, max/min elevation, elevation samples, and an estimated walking time'.
Documented attack patterns abuse exactly the kind of access get_hike_profile 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_hike_profile:
{
"version": "1",
"default": "deny",
"tools": {
"get_hike_profile": {}
}
}get_hike_profile 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.
Given a WGS84 GeoJSON LineString (usually the geometry from get_named_route), return distance, ascent, descent, max/min elevation, elevation samples, and an estimated walking time using the SAC/DAV formula. 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_hike_profile: 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_hike_profile 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_hike_profile 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_hike_profile. 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_hike_profile 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.