Re-index the music folder so songs the user dropped in by hand become playable. Returns counts.
AI agents invoke radio_rescan to trigger actions in GTAV-CLAUDE-MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation (re-scanning/re-indexing a folder) rather than simply reading or writing data. It executes a background scan process and returns counts. The blast radius is low since it only affects the in-game music index, but it does trigger an operation with side effects beyond a simple read or write.
From the tool's definition Re-index the music folder so songs the user dropped in by hand become playable
Attacks that exploit this kind of access
Re-index the music folder so songs the user dropped in by hand become playable. Returns counts. It is categorised as a Execute tool in the GTAV-CLAUDE-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the GTAV-CLAUDE- MCP server in PolicyLayer and add a rule for radio_rescan: 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.
radio_rescan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the radio_rescan 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 radio_rescan. 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.
radio_rescan 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 →