Start charging (vehicle must be plugged in).
AI agents invoke tesla_charge_start to trigger actions in Mcp Teslamate Fleet. 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 sends a command to a Tesla vehicle to begin charging, which is an external real-world action. While it is reversible (charging can be stopped), it initiates a physical process on an external system. It is Execute-level because it triggers an external operation whose effect depends on the vehicle's state and connection.
From the tool's definition 'Start charging (vehicle must be plugged in)' — triggers an external physical operation on a vehicle
Attacks that exploit this kind of access
Start charging (vehicle must be plugged in). It is categorised as a Execute tool in the Mcp Teslamate Fleet MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Teslamate Fleet MCP server in PolicyLayer and add a rule for tesla_charge_start: 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_charge_start 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 tesla_charge_start 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_charge_start. 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_charge_start 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 →