Get details of a specific notification.
AI agents call fizzy_get_notification to retrieve information from Fizzy Do MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves notification data from the Fizzy task management system. The verb 'Get' and the passive nature of querying notification details classify this as a Read operation. There is no data modification, deletion, code execution, or financial impact. Severity is low because notifications are typically non-sensitive metadata about user activities.
From the tool's definition Tool name 'fizzy_get_notification' and description 'Get details of a specific notification' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get details of a specific notification. It is categorised as a Read tool in the Fizzy Do MCP MCP Server, which means it retrieves data without modifying state.
Register the Fizzy Do MCP server in PolicyLayer and add a rule for fizzy_get_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 Fizzy Do MCP. Nothing to install.
fizzy_get_notification 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 fizzy_get_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 fizzy_get_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.
fizzy_get_notification is provided by the Fizzy Do MCP server (ryanyogan/fizzy-do-mcp). 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 →