This record as markdown: /tools/heznpc-airmcp/mark-message-read.md
What mark_message_read does on AirMCP
AI agents use mark_message_read to create or update resources in AirMCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AirMCP environment.
Why mark_message_read is rated Medium
The tool updates email message state, which is a reversible modification of data. It does not delete, execute arbitrary operations, move money, or trigger destructive actions. While it changes system state, the change is easily undone by toggling the flag back. This fits the Write category (creates or modifies data reversibly).
From the tool's definition Tool description: 'Mark an email message as read or unread.' This modifies email message metadata state (read/unread flag) reversibly without deleting or executing code.
Attacks that exploit this kind of access
The rule that runs mark_message_read safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mark_message_read, this is the rule to start with:
mark_message_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 AirMCP, apply this rule, and every mark_message_read call is checked against it from then on.
Questions about mark_message_read
Mark an email message as read or unread. It is categorised as a Write tool in the AirMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Air MCP server in PolicyLayer and add a rule for mark_message_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 AirMCP. Nothing to install.
mark_message_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_message_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_message_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_message_read is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue