Native DB status: edition (legacy/enhanced), how many natives are callable, known-bad list.
AI agents call native_db_status 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 tool queries and reports metadata about available game natives and their status. It performs no state changes, executes no code, and triggers no game actions. It is a straightforward informational read operation with minimal security impact.
From the tool's definition Tool description specifies 'Native DB status: edition (legacy/enhanced), how many natives are callable, known-bad list' - purely retrieves status information about the native database without modifying or executing anything.
Attacks that exploit this kind of access
Native DB status: edition (legacy/enhanced), how many natives are callable, known-bad list. 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_db_status: 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_db_status 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_db_status 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_db_status. 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_db_status 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 →