get_notification_details
Get detailed information for a specific GitHub notification, always call this tool when the user asks for details about a specific notification, if you don't know the ID list notifications first.
This record as markdown: /tools/github/get-notification-details.md
What get_notification_details does on GitHub
AI agents call get_notification_details to retrieve information from GitHub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
notificationID | string | — | The ID of the notification |
Parameters from the server's own tool schema.
Why get_notification_details is rated Low
This tool queries and retrieves notification details from GitHub without creating, modifying, deleting, or executing any operations. It is a pure read operation that returns information to the user. The severity is low because retrieving notification metadata poses minimal security risk even if misused by an AI agent.
From the tool's definition Tool description explicitly states 'Get detailed information for a specific GitHub notification' - a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_notification_details safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_notification_details, this is the rule to start with:
get_notification_details is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every get_notification_details call is checked against it from then on.
Questions about get_notification_details
Get detailed information for a specific GitHub notification, always call this tool when the user asks for details about a specific notification, if you don't know the ID list notifications first. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
get_notification_details accepts 1 parameter: notificationID. The full parameter table on this page comes from the server's own tool schema.
Register the GitHub MCP server in PolicyLayer and add a rule for get_notification_details: 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 GitHub. Nothing to install.
get_notification_details 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 get_notification_details 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 get_notification_details. 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.
get_notification_details is provided by the GitHub MCP server (oci:ghcr.io/github/github-mcp-server:1.3.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue