fizzy_mark_notification_read · Fizzy Do MCP: Risk & Policy

WHAT IT DOES

What fizzy_mark_notification_read does on Fizzy Do MCP

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

WHY IT NEEDS A POLICY

Why fizzy_mark_notification_read needs a policy

Marking a notification as read is a reversible write operation that modifies the state of a notification object without deleting it or triggering external actions. The user can unmark it or interact with the notification again if needed. The blast radius is minimal since it only affects notification metadata for the authenticated user, with no financial, destructive, or execution implications.

From the tool's definition Tool name includes 'mark' and description states 'Mark a specific notification as read' — this is a state modification operation that changes notification status from unread to read.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

fizzy_mark_notification_read Rate-limited

fizzy_mark_notification_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": {
    "fizzy_mark_notification_read": {
      "limits": [
        {
          "counter": "fizzy_mark_notification_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 Fizzy Do MCP, so you can run agents against it safely.

FAQ

Questions about fizzy_mark_notification_read

What does the fizzy_mark_notification_read tool do? +

Mark a specific notification as read. It is categorised as a Write tool in the Fizzy Do MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on fizzy_mark_notification_read? +

Register the Fizzy Do MCP server in PolicyLayer and add a rule for fizzy_mark_notification_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 Fizzy Do MCP. Nothing to install.

What risk level is fizzy_mark_notification_read? +

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

Can I rate-limit fizzy_mark_notification_read? +

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

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

fizzy_mark_notification_read is provided by the Fizzy Do MCP server (ryanyogan/fizzy-do-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.