list_repo_notifications

List the authenticated user

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/list-repo-notifications.md

WHAT IT DOES

What list_repo_notifications does on Forgejo

AI agents call list_repo_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 list_repo_notifications is rated Low

Retrieves user notification data with no side effects or modifications to system state.

From the tool's definition List the authenticated user notifications for repositories.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_repo_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 list_repo_notifications, this is the rule to start with:

list_repo_notifications Allowed

list_repo_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": {
    "list_repo_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 list_repo_notifications call is checked against it from then on.

FAQ

Questions about list_repo_notifications

What does the list_repo_notifications tool do? +

List the authenticated user. 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 list_repo_notifications? +

Register the Forgejo MCP server in PolicyLayer and add a rule for list_repo_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 list_repo_notifications? +

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

Can I rate-limit list_repo_notifications? +

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

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

list_repo_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

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

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