dismiss_notification
Dismiss a notification by marking it as read or done
This record as markdown: /tools/github/dismiss-notification.md
What dismiss_notification does on GitHub
AI agents use dismiss_notification to create or update resources in GitHub, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
state | string | — | The new state of the notification (read/done) |
threadID | string | — | The ID of the notification thread |
Parameters from the server's own tool schema.
Why dismiss_notification is rated Medium
This tool modifies the state of a notification (marking it as read or done), which is a reversible write operation. The blast radius is very low as it only affects notification status, not any substantive data or code.
From the tool's definition Dismiss a notification by marking it as read or done
Attacks that exploit this kind of access
The rule that runs dismiss_notification 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 dismiss_notification, this is the rule to start with:
dismiss_notification 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.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every dismiss_notification call is checked against it from then on.
Questions about dismiss_notification
Dismiss a notification by marking it as read or done. It is categorised as a Write tool in the GitHub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
dismiss_notification accepts 2 parameters: state, threadID. 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 dismiss_notification: 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.
dismiss_notification is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the dismiss_notification 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 dismiss_notification. 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.
dismiss_notification 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