miro_list_items
List the items (notes, shapes, text) on a Miro board.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/miro-list-items.md
What miro_list_items does on UnClick
AI agents call miro_list_items 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 item type (e.g. sticky_note, shape, text) |
limit | number | — | Items to return (max 50, default 25) |
board_id | string | Yes | Miro board id |
access_token | string | Yes | Miro access token |
Parameters from the server's own tool schema.
Why miro_list_items is rated Low
The tool retrieves and queries existing data from a Miro board without creating, modifying, deleting, or executing any operations. This is a straightforward read operation with minimal risk; the blast radius is limited to information disclosure of board contents the agent already has access to.
From the tool's definition Tool name explicitly states 'list_items' and description says 'List the items (notes, shapes, text) on a Miro board' — a pure retrieval operation with no side effects.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs miro_list_items 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 miro_list_items, this is the rule to start with:
miro_list_items 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 miro_list_items call is checked against it from then on.
Questions about miro_list_items
List the items (notes, shapes, text) on a Miro board. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
miro_list_items accepts 4 parameters: type, limit, board_id, access_token. Required: board_id, 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 miro_list_items: 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.
miro_list_items 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 miro_list_items 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 miro_list_items. 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.
miro_list_items 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