Get the count of unread notifications.
AI agents call get_unread_notification_count to retrieve information from Payoza MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns notification count data without modifying, deleting, or executing any operations. It is a straightforward read operation. While the server context involves financial transactions (crypto payments), this specific tool poses minimal risk as it merely retrieves notification metadata.
From the tool's definition Tool name 'get_unread_notification_count' and description 'Get the count of unread notifications' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get the count of unread notifications. It is categorised as a Read tool in the Payoza MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Payoza MCP Server MCP server in PolicyLayer and add a rule for get_unread_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 Payoza MCP Server. Nothing to install.
get_unread_notification_count 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_unread_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.
Set action: deny in the PolicyLayer policy for get_unread_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.
get_unread_notification_count is provided by the Payoza MCP Server MCP server (payoza/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 →