mapbox_get_static_map
Generate a static map image URL for a given location using Mapbox.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/mapbox-get-static-map.md
What mapbox_get_static_map does on UnClick
AI agents call mapbox_get_static_map to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
zoom | number | — | Zoom level (0-22, default: 12) |
style | string | — | Map style (default: mapbox/streets-v11) |
width | number | — | Image width in px (max: 1280, default: 600) |
height | number | — | Image height in px (max: 1280, default: 400) |
retina | boolean | — | Return @2x high-DPI image |
latitude | number | Yes | Center latitude |
longitude | number | Yes | Center longitude |
access_token | string | Yes | Mapbox access token |
Parameters from the server's own tool schema.
Why mapbox_get_static_map is rated Low
The tool performs a read-only operation: it takes location parameters and returns a static map image URL. There are no side effects, no data modification, no code execution, and no destructive or financial implications. The only potential low-severity risk is information disclosure if sensitive location data is queried, but this is inherent to any mapping service and classified as a standard Read operation.
From the tool's definition Tool description states 'Generate a static map image URL for a given location using Mapbox.' This is a retrieval operation that generates and returns a map image without modifying any data or triggering external actions beyond rendering a map visualization.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs mapbox_get_static_map safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mapbox_get_static_map, this is the rule to start with:
mapbox_get_static_map is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every mapbox_get_static_map call is checked against it from then on.
Questions about mapbox_get_static_map
Generate a static map image URL for a given location using Mapbox. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
mapbox_get_static_map accepts 8 parameters: zoom, style, width, height, retina, latitude, longitude, access_token. Required: latitude, longitude, access_token. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for mapbox_get_static_map: 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 UnClick. Nothing to install.
mapbox_get_static_map 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 mapbox_get_static_map 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 mapbox_get_static_map. 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.
mapbox_get_static_map is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue