Show debug information about your Tesla vehicles (ids, vins, state).
AI agents call debug_vehicles to retrieve information from Tesla MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays debug information (vehicle IDs, VINs, and state) without creating, modifying, deleting, or executing actions on vehicles. It is a read-only query operation with no side effects. The severity is low as the information exposed (IDs, VINs, state) is already accessible through other tools like get_vehicle_status and list_vehicles, and debug data typically poses minimal risk if disclosed.
From the tool's definition Tool name 'debug_vehicles' with description 'Show debug information about your Tesla vehicles (ids, vins, state)' indicates retrieval of vehicle metadata without modification or control.
Attacks that exploit this kind of access
Show debug information about your Tesla vehicles (ids, vins, state). It is categorised as a Read tool in the Tesla MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tesla MCP Server MCP server in PolicyLayer and add a rule for debug_vehicles: 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 Tesla MCP Server. Nothing to install.
debug_vehicles 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 debug_vehicles 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 debug_vehicles. 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.
debug_vehicles is provided by the Tesla MCP Server MCP server (sara3/tesla-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 →