razz_read_dm_history
Read message history with a specific user.
This record as markdown: /tools/io-github-razz-games-razz/razz-read-dm-history.md
What razz_read_dm_history does on Razz Games
AI agents call razz_read_dm_history 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 |
|---|---|---|---|
before | number | — | Load messages before this timestamp (pagination) |
peerId | string | Yes | Account ID of the other user |
Parameters from the server's own tool schema.
Why razz_read_dm_history is rated Low
This tool retrieves existing message history between users. It is purely informational (Read category), poses minimal risk to the gaming platform, and does not modify, execute operations, or affect financial transactions. Severity is low because reading message history cannot cause harm beyond potential privacy concerns, which are mitigated by user consent in a gaming context.
From the tool's definition Tool name contains 'read' and description states 'Read message history' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs razz_read_dm_history 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_read_dm_history, this is the rule to start with:
razz_read_dm_history 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_read_dm_history call is checked against it from then on.
Questions about razz_read_dm_history
Read message history with a specific user. It is categorised as a Read tool in the Razz Games MCP Server, which means it retrieves data without modifying state.
razz_read_dm_history accepts 2 parameters: before, peerId. Required: peerId. 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_read_dm_history: 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_read_dm_history 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_read_dm_history 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_read_dm_history. 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_read_dm_history 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