AI agents call render_battlefield to retrieve information from ChatRPG without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves and displays current game state as a visual ASCII map. It reads existing data (positions, obstacles, terrain) and returns a visualization with no side effects, modifications, or destructive actions.
From the tool's definition Render an ASCII map of the current combat state showing participant positions, obstacles, and terrain. Returns a text-based grid visualization.
Attacks that exploit this kind of access
Render an ASCII map of the current combat state showing participant positions, obstacles, and terrain. Returns a text-based grid visualization. It is categorised as a Read tool in the ChatRPG MCP Server, which means it retrieves data without modifying state.
Register the ChatRPG MCP server in PolicyLayer and add a rule for render_battlefield: 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 ChatRPG. Nothing to install.
render_battlefield 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 render_battlefield 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 render_battlefield. 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.
render_battlefield is provided by the ChatRPG MCP server (mnehmos/mnehmos.chatrpg.game). 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 →