mark-notification-read · NestJS MCP Server Module MCP

WHAT IT DOES

What mark-notification-read does on NestJS MCP Server Module

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

WHY IT NEEDS A POLICY

Why mark-notification-read needs a policy

This tool modifies notification data (changes read status) but does so reversibly—the action can be undone by marking the notification as unread. It has no destructive, financial, or code execution implications. The blast radius is minimal: a misused tool could mark wrong notifications as read, causing minor user confusion or information leakage, but cannot delete data or cause irreversible harm.

From the tool's definition Tool name 'mark-notification-read' and description 'Mark a notification as read' indicate a state modification operation that updates a notification record to reflect a read status.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mark-notification-read Rate-limited

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": {
    "mark-notification-read": {
      "limits": [
        {
          "counter": "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 NestJS MCP Server Module, so you can run agents against it safely.

FAQ

Questions about mark-notification-read

What does the mark-notification-read tool do? +

Mark a notification as read. It is categorised as a Write tool in the NestJS MCP Server Module 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-notification-read? +

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

What risk level is mark-notification-read? +

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 mark-notification-read? +

Yes. Add a rate_limit block to the 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 mark-notification-read completely? +

Set action: deny in the PolicyLayer policy for 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 mark-notification-read? +

mark-notification-read is provided by the NestJS MCP Server Module MCP server (rekog-labs/mcp-nest). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.