razz_get_recent_activity
Get recent platform-wide activity feed (game results, match outcomes, rain, tips, staking). Public - shows all players, not just your own games. Great for reporting on what's happening on the platform.
This record as markdown: /tools/io-github-razz-games-razz/razz-get-recent-activity.md
What razz_get_recent_activity does on Razz Games
AI agents call razz_get_recent_activity 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | — | Filter by event type: game_win, game_loss, match_result, rain, tip, staking_win, staking_loss, hexwar |
limit | number | — | Max events to return (default 30) |
gameType | string | — | Filter by game type: crash, dice, flip, rps, plinko, limbo, tower, mines, hexwar |
Parameters from the server's own tool schema.
Why razz_get_recent_activity is rated Low
This tool retrieves and queries historical activity data from the platform. It does not create, modify, delete, or execute any operations. The activity feed is described as public and historical (game results, match outcomes, etc.), making it a pure Read operation. While the server involves real SOL wagering, this specific tool only accesses publicly available information without financial transactional capability.
From the tool's definition Tool description states 'Get recent platform-wide activity feed' and 'Public - shows all players'. The verb 'Get' and the read-only nature of an activity feed indicate data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs razz_get_recent_activity 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_get_recent_activity, this is the rule to start with:
razz_get_recent_activity 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_get_recent_activity call is checked against it from then on.
Questions about razz_get_recent_activity
Get recent platform-wide activity feed (game results, match outcomes, rain, tips, staking). Public - shows all players, not just your own games. Great for reporting on what's happening on the platform. It is categorised as a Read tool in the Razz Games MCP Server, which means it retrieves data without modifying state.
razz_get_recent_activity accepts 3 parameters: type, limit, gameType. The full parameter table on this page comes from the server's own tool schema.
Register the Razz Games MCP server in PolicyLayer and add a rule for razz_get_recent_activity: 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_get_recent_activity 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_get_recent_activity 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_get_recent_activity. 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_get_recent_activity 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