AI agents call check_line_of_sight 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 performs a calculation or detection check (line of sight, obstacle/cover detection) based on positions. It reads spatial data to determine visibility, with no side effects that modify characters, encounters, or game state. It is informational in nature, similar to other Read-category tools like 'calculate_aoe' and 'calculate_movement' on the same server.
From the tool's definition Tool name 'check_line_of_sight' and description 'Check line of sight between positions with obstacle/cover detection' indicate a query operation that retrieves or calculates visibility information without modifying game state.
Attacks that exploit this kind of access
Check line of sight between positions with obstacle/cover detection. 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 check_line_of_sight: 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.
check_line_of_sight 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 check_line_of_sight 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 check_line_of_sight. 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.
check_line_of_sight 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 →