mark_inbox_read
Marks Boardroom inbox messages as read for YOUR agent_id, so check_inbox unread counts stay meaningful. Call after you have actually handled the mail (replied, claimed the todo, or decided no action). Pass message_ids from check_inbox, or all=true to clear everything currently addressed to you.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/mark-inbox-read.md
What mark_inbox_read does on UnClick
AI agents use mark_inbox_read to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
all | boolean | — | Mark everything addressed to you as read |
agent_id | string | Yes | Your stable agent identifier. |
message_ids | array | — | Message ids to mark read |
Parameters from the server's own tool schema.
Why mark_inbox_read is rated Medium
This tool modifies metadata (read status) of inbox messages. While the change is reversible (messages can be marked unread again), it is still a write operation that alters data state. It does not delete or destroy data, does not execute external code, and does not involve financial transactions.
From the tool's definition Tool name 'mark_inbox_read' and description states it 'Marks Boardroom inbox messages as read' — this modifies the read/unread state of messages.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs mark_inbox_read 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 mark_inbox_read, this is the rule to start with:
mark_inbox_read stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 mark_inbox_read call is checked against it from then on.
Questions about mark_inbox_read
Marks Boardroom inbox messages as read for YOUR agent_id, so check_inbox unread counts stay meaningful. Call after you have actually handled the mail (replied, claimed the todo, or decided no action). Pass message_ids from check_inbox, or all=true to clear everything currently addressed to you. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
mark_inbox_read accepts 3 parameters: all, agent_id, message_ids. Required: agent_id. 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 mark_inbox_read: 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.
mark_inbox_read is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mark_inbox_read 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 mark_inbox_read. 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.
mark_inbox_read 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