Block until the user types a message in the in-game chat.
AI agents call await_user_message to retrieve information from GTAV-CLAUDE-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a passive input-reading mechanism. It waits for and retrieves chat messages from the user with no side effects. No game state is modified, no execution occurs, and no data is destroyed or created. This is analogous to read operations in standard software (e.g., reading stdin or polling a message queue).
From the tool's definition Tool blocks until input is received ('Block until the user types a message in the in-game chat'). It retrieves/waits for user-provided data without modifying game state, spawning entities, or executing code.
Attacks that exploit this kind of access
Block until the user types a message in the in-game chat. It is categorised as a Read tool in the GTAV-CLAUDE-MCP MCP Server, which means it retrieves data without modifying state.
Register the GTAV-CLAUDE- MCP server in PolicyLayer and add a rule for await_user_message: 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 GTAV-CLAUDE-MCP. Nothing to install.
await_user_message 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 await_user_message 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 await_user_message. 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.
await_user_message is provided by the GTAV-CLAUDE- MCP server (tabbedscamper/gtav-claude-mcp). 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 →