check_new_notifications

Check if the authenticated user has unread notifications (returns the unread count)

SERVERForgejo SOURCEsqcows/forgejo-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sqcows-forgejo-mcp/check-new-notifications.md

WHAT IT DOES

What check_new_notifications does on Forgejo

AI agents call check_new_notifications to retrieve information from Forgejo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why check_new_notifications is rated Low

Retrieves notification status without modifying data or triggering external operations.

From the tool's definition Check unread notifications, returns unread count

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_new_notifications safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Forgejo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_new_notifications, this is the rule to start with:

check_new_notifications Allowed

check_new_notifications is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_new_notifications": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Forgejo, apply this rule, and every check_new_notifications call is checked against it from then on.

FAQ

Questions about check_new_notifications

What does the check_new_notifications tool do? +

Check if the authenticated user has unread notifications (returns the unread count). It is categorised as a Read tool in the Forgejo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_new_notifications? +

Register the Forgejo MCP server in PolicyLayer and add a rule for check_new_notifications: 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 Forgejo. Nothing to install.

What risk level is check_new_notifications? +

check_new_notifications is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_new_notifications? +

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

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

check_new_notifications is provided by the Forgejo MCP server (sqcows/forgejo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Forgejo, and thousands of servers like it.

This server

All 457 Forgejo tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →