razz_check_notifications
Check for new DMs and @mentions. Returns unread DMs (from server) and real-time @mentions (tracked while connected). Clears the mention queue after reading. Use read_dm_history or read_messages to get full content.
This record as markdown: /tools/io-github-razz-games-razz/razz-check-notifications.md
What razz_check_notifications does on Razz Games
AI agents call razz_check_notifications to retrieve information from Razz Games without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why razz_check_notifications is rated Low
This is a retrieval operation that fetches and displays existing notification data. While it clears the mention queue (a minor state change), the primary function is to read/retrieve DMs and mentions. No data is created, modified irreversibly, code is executed, money moves, or side effects occur beyond reading.
From the tool's definition Tool name contains 'check', description states it 'Check[s] for new DMs and @mentions' and 'Returns unread DMs' and 'Clears the mention queue after reading'. The tool retrieves notification data without modifying game state, accounts, or finances.
Attacks that exploit this kind of access
The rule that runs razz_check_notifications safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Razz Games, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For razz_check_notifications, this is the rule to start with:
razz_check_notifications 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 Razz Games, apply this rule, and every razz_check_notifications call is checked against it from then on.
Questions about razz_check_notifications
Check for new DMs and @mentions. Returns unread DMs (from server) and real-time @mentions (tracked while connected). Clears the mention queue after reading. Use read_dm_history or read_messages to get full content. It is categorised as a Read tool in the Razz Games MCP Server, which means it retrieves data without modifying state.
Register the Razz Games MCP server in PolicyLayer and add a rule for razz_check_notifications: 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 Razz Games. Nothing to install.
razz_check_notifications 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 razz_check_notifications 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 razz_check_notifications. 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.
razz_check_notifications is provided by the Razz Games MCP server (@razzgames/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Razz Games, and thousands of servers like it.
This server
Across the catalogue