This record as markdown: /tools/io-github-portel-dev-ncp/mark-read.md
What mark_read does on Ncp
AI agents use mark_read to create or update resources in Ncp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ncp environment.
Why mark_read is rated Medium
This tool modifies data (email read status) in a reversible manner. It does not retrieve/query (Read), execute arbitrary code (Execute), delete data (Destructive), or involve financial transactions (Financial). The severity is low because changing email read status has minimal blast radius—it affects only email metadata and can be easily undone by marking as unread.
From the tool's definition Tool name 'mark_read' and description 'Mark emails as read' indicate modification of email state/metadata. The action changes an email's read status from unread to read.
Attacks that exploit this kind of access
The rule that runs mark_read safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mark_read, this is the rule to start with:
mark_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 Ncp, apply this rule, and every mark_read call is checked against it from then on.
Questions about mark_read
Mark emails as read. It is categorised as a Write tool in the Ncp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ncp MCP server in PolicyLayer and add a rule for mark_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 Ncp. Nothing to install.
mark_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_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_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_read is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue