fizzy_notification_count

Get the count of notifications (total and unread).

Server Fizzy Do MCP ryanyogan/fizzy-do-mcp
Category Read
Risk class Low
Parameters 00 required

What fizzy_notification_count does on Fizzy Do MCP

AI agents call fizzy_notification_count 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.

Why fizzy_notification_count needs a policy

This tool retrieves notification count data without modifying, creating, or deleting any information. It is a simple query operation that only reads existing state, matching the 'Read' category definition.

From the tool's definition Tool name 'fizzy_notification_count' and description 'Get the count of notifications (total and unread)' indicate a retrieval operation with no side effects.

Questions about fizzy_notification_count

What does the fizzy_notification_count tool do? +

Get the count of notifications (total and unread). It is categorised as a Read tool in the Fizzy Do MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fizzy_notification_count? +

Register the Fizzy Do MCP server in PolicyLayer and add a rule for fizzy_notification_count: 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.

What risk level is fizzy_notification_count? +

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

Can I rate-limit fizzy_notification_count? +

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

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

fizzy_notification_count 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.