Mark an entry as unread.
AI agents use mark_unread_tool to create or update resources in MCP Feed Reader — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Feed Reader environment.
This tool modifies data (marking an entry's read status) in a reversible manner. The action can be undone by marking it read again. It does not delete, destroy, or execute code—it simply updates a boolean or status field in the SQLite backend. This is a classic Write operation with minimal blast radius.
From the tool's definition Tool name 'mark_unread_tool' and description 'Mark an entry as unread' indicate a state change operation on feed entries.
Attacks that exploit this kind of access
Mark an entry as unread. It is categorised as a Write tool in the MCP Feed Reader MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Feed Reader MCP server in PolicyLayer and add a rule for mark_unread_tool: 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 MCP Feed Reader. Nothing to install.
mark_unread_tool 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_unread_tool 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_unread_tool. 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_unread_tool is provided by the MCP Feed Reader MCP server (pypi:mcp-feed-reader-crunchtools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →