Current vehicle state — battery, range, location, climate, odometer.
AI agents call tesla_status to retrieve information from Mcp Teslamate Fleet without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves current vehicle status information without triggering any vehicle controls, modifications, or external actions. It is purely informational. The sibling tools like 'tesla_charge_start', 'tesla_charge_stop', and 'tesla_climate_on/off' demonstrate that command execution would be implemented as separate tools. Low severity reflects minimal risk from reading vehicle state data.
From the tool's definition Tool name 'tesla_status' and description 'Current vehicle state — battery, range, location, climate, odometer' indicate retrieval of vehicle telemetry data with no modification or command execution.
Attacks that exploit this kind of access
Current vehicle state — battery, range, location, climate, odometer. It is categorised as a Read tool in the Mcp Teslamate Fleet MCP Server, which means it retrieves data without modifying state.
Register the Mcp Teslamate Fleet MCP server in PolicyLayer and add a rule for tesla_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 Mcp Teslamate Fleet. Nothing to install.
tesla_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 tesla_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 tesla_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.
tesla_status is provided by the Mcp Teslamate Fleet MCP server (lodordev/mcp-teslamate-fleet). 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 →