New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

mark_notifications_read

Mark one or more notifications as read. Pass all=true to mark everything read, or pass an array of IDs to mark specific items.

SERVERTodo for AI MCP Server SOURCEtodo-for-ai/todo-for-ai-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/todo-for-ai-todo-for-ai-mcp/mark-notifications-read.md

What mark_notifications_read does on Todo for AI MCP Server

AI agents use mark_notifications_read to create or update resources in Todo for AI MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todo for AI MCP Server environment.

Why mark_notifications_read is rated Medium

An AI agent can call mark_notifications_read faster than any human can review: one bad instruction and it creates or modifies resources in Todo for AI MCP Server by the hundred, each call as confident as the last.

Risk signalsBulk/mass operation — affects multiple targets

Questions about mark_notifications_read

What does the mark_notifications_read tool do? +

Mark one or more notifications as read. Pass all=true to mark everything read, or pass an array of IDs to mark specific items. It is categorised as a Write tool in the Todo for AI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mark_notifications_read? +

Register the Todo for AI MCP Server MCP server in PolicyLayer and add a rule for mark_notifications_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 Todo for AI MCP Server. Nothing to install.

What risk level is mark_notifications_read? +

mark_notifications_read is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit mark_notifications_read? +

Yes. Add a rate_limit block to the mark_notifications_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.

How do I block mark_notifications_read completely? +

Set action: deny in the PolicyLayer policy for mark_notifications_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.

What MCP server provides mark_notifications_read? +

mark_notifications_read is provided by the Todo for AI MCP Server MCP server (todo-for-ai/todo-for-ai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Todo for AI MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Todo for AI MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.