Get your Tesla
AI agents call get_vehicle_location 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 real-time location data from a connected vehicle. While classified as Read (no data modification), severity is elevated to medium because precise vehicle location exposes significant privacy and physical security risks—an AI agent with this capability could enable stalking, theft planning, or unauthorized vehicle tracking.
From the tool's definition Tool name 'get_vehicle_location' and description 'Get your Tesla' indicate retrieval of vehicle location data with no modification. Server description confirms it 'retrieve[s] real-time status updates'.
Attacks that exploit this kind of access
Get your Tesla. 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 get_vehicle_location: 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.
get_vehicle_location 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 get_vehicle_location 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 get_vehicle_location. 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.
get_vehicle_location 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 →