moltbook_mark_notifications_read · Moltbook MCP Server MCP

WHAT IT DOES

What moltbook_mark_notifications_read does on Moltbook MCP Server

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

WHY IT NEEDS A POLICY

Why moltbook_mark_notifications_read needs a policy

This tool modifies data (notification read status) in a reversible manner. The user can mark notifications as unread again. It has no destructive, financial, or code execution implications. The blast radius is minimal—marking notifications as read affects only the user's notification state and cannot damage data or systems. This is a standard Write operation.

From the tool's definition Tool name 'moltbook_mark_notifications_read' and description 'Mark all notifications as read' indicate a state modification operation that updates notification records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

moltbook_mark_notifications_read Rate-limited

moltbook_mark_notifications_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": {
    "moltbook_mark_notifications_read": {
      "limits": [
        {
          "counter": "moltbook_mark_notifications_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 Moltbook MCP Server, so you can run agents against it safely.

FAQ

Questions about moltbook_mark_notifications_read

What does the moltbook_mark_notifications_read tool do? +

Mark all notifications as read. It is categorised as a Write tool in the Moltbook 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 moltbook_mark_notifications_read? +

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

What risk level is moltbook_mark_notifications_read? +

moltbook_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 moltbook_mark_notifications_read? +

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

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

moltbook_mark_notifications_read is provided by the Moltbook MCP Server MCP server (thebenlamm/moltbook-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.