todoist_notifications_mark_all_read

WHAT IT DOES

What todoist_notifications_mark_all_read does on Mcp Todoist

AI agents use todoist_notifications_mark_all_read to create or update resources in Mcp Todoist — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Todoist environment.

WHY IT NEEDS A POLICY

Why todoist_notifications_mark_all_read needs a policy

This tool changes the read status of notifications, which is a reversible modification of existing data. It does not delete, execute arbitrary code, involve financial transactions, or trigger external operations. The blast radius is minimal as it only affects the user's own notification state, and the action can be undone by future interactions.

From the tool's definition Tool name indicates 'mark_all_read' which modifies the state of notifications; description confirms 'Mark all notifications as read' — this updates notification records without deleting or destroying data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

todoist_notifications_mark_all_read Rate-limited

todoist_notifications_mark_all_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "todoist_notifications_mark_all_read": {
      "limits": [
        {
          "counter": "todoist_notifications_mark_all_read_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mcp Todoist, so you can run agents against it safely.

FAQ

Questions about todoist_notifications_mark_all_read

What does the todoist_notifications_mark_all_read tool do? +

Mark all notifications as read. It is categorised as a Write tool in the Mcp Todoist MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on todoist_notifications_mark_all_read? +

Register the Mcp Todoist MCP server in PolicyLayer and add a rule for todoist_notifications_mark_all_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 Mcp Todoist. Nothing to install.

What risk level is todoist_notifications_mark_all_read? +

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

Can I rate-limit todoist_notifications_mark_all_read? +

Yes. Add a rate_limit block to the todoist_notifications_mark_all_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 todoist_notifications_mark_all_read completely? +

Set action: deny in the PolicyLayer policy for todoist_notifications_mark_all_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 todoist_notifications_mark_all_read? +

todoist_notifications_mark_all_read is provided by the Mcp Todoist MCP server (@greirson/mcp-todoist). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.