This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/mapbox-list-tilesets.md
What mapbox_list_tilesets does on UnClick
AI agents call mapbox_list_tilesets 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 |
|---|---|---|---|
type | string | — | Filter by tileset type |
limit | number | — | Max tilesets to return (max: 500) |
username | string | Yes | Mapbox username |
access_token | string | Yes | Mapbox access token |
Parameters from the server's own tool schema.
Why mapbox_list_tilesets is rated Low
The tool retrieves and enumerates existing tilesets without modifying, deleting, or executing any operations. It is a standard data retrieval operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name and description indicate 'List' operation on Mapbox tilesets: 'List Mapbox tilesets owned by a user.' This is a read-only query with no side effects.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs mapbox_list_tilesets 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_list_tilesets, this is the rule to start with:
mapbox_list_tilesets 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_list_tilesets call is checked against it from then on.
Questions about mapbox_list_tilesets
List Mapbox tilesets owned by a user. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
mapbox_list_tilesets accepts 4 parameters: type, limit, username, access_token. Required: username, 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_list_tilesets: 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_list_tilesets 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_list_tilesets 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_list_tilesets. 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_list_tilesets 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