Return the raw Avalanche.org map-layer GeoJSON FeatureCollection for a specific avalanche center ID. Supports an optional historic day (YYYY-MM-DD).
Single-target operation
Part of the Avalanche Org MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call raw_map_layer_by_avalanche_center to retrieve information from Avalanche Org without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though raw_map_layer_by_avalanche_center only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
raw_map_layer_by_avalanche_center:
rules:
- action: allowSee the full Avalanche Org policy for all 4 tools.
Agents calling read-class tools like raw_map_layer_by_avalanche_center have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Return the raw Avalanche.org map-layer GeoJSON FeatureCollection for a specific avalanche center ID. Supports an optional historic day (YYYY-MM-DD).. It is categorised as a Read tool in the Avalanche Org MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for raw_map_layer_by_avalanche_center. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Avalanche Org MCP server.
raw_map_layer_by_avalanche_center 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 raw_map_layer_by_avalanche_center rule in your Intercept 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 Intercept policy for raw_map_layer_by_avalanche_center. 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.
raw_map_layer_by_avalanche_center is provided by the Avalanche Org MCP server (avalanche-org-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept