Get a native's params (order + types), return type, namespace, flags, and doc comment.
AI agents call native_info 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 lookup/query tool that retrieves information about game natives. It has no side effects, does not execute code, and does not modify game state or data. The worst-case misuse would be information disclosure, which is low severity in a gaming context where the native function signatures are not sensitive data.
From the tool's definition Tool description states 'Get a native's params... return type, namespace, flags, and doc comment' — purely retrieving metadata about game native functions without executing or modifying anything.
Attacks that exploit this kind of access
Get a native's params (order + types), return type, namespace, flags, and doc comment. 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 native_info: 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.
native_info 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 native_info 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 native_info. 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.
native_info 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 →