AI agents call list_user_notifications to retrieve information from Mcp Gitee without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | number | — | Page number |
type | string | — | Filter notifications of a specified type, all: all, event: event notification, referer: @ notification |
since | string | — | Only list notifications updated after the given time, requiring the time format to be ISO 8601 |
before | string | — | Only list notifications updated before the given time, requiring the time format to be ISO 8601 |
unread | boolean | — | Only list unread notifications |
per_page | number | — | Number of results per page |
participating | boolean | — | Only list notifications where the user is directly participating or mentioned |
Parameters from the server's own tool schema.
The tool retrieves notification data for the authenticated user. The verb 'list' and the read-only nature of fetching notifications indicate this is a Read operation. There is no modification, deletion, or external execution involved. Severity is low because notifications are informational metadata with limited blast radius if exposed.
From the tool's definition Tool name is 'list_user_notifications' and description states 'List all notifications for authorized user' — this is a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List all notifications for authorized user. It is categorised as a Read tool in the Mcp Gitee MCP Server, which means it retrieves data without modifying state.
list_user_notifications accepts 7 parameters: page, type, since, before, unread, per_page, participating. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Gitee MCP server in PolicyLayer and add a rule for list_user_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 Mcp Gitee. Nothing to install.
list_user_notifications is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_user_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.
Set action: deny in the PolicyLayer policy for list_user_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.
list_user_notifications is provided by the Mcp Gitee MCP server (@gitee/mcp-gitee). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →