tesla_charge_stop · Mcp Teslamate Fleet MCP: Risk & Policy

WHAT IT DOES

What tesla_charge_stop does on Mcp Teslamate Fleet

AI agents invoke tesla_charge_stop 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.

WHY IT NEEDS A POLICY

Why tesla_charge_stop needs a policy

This tool sends a real-time command to a Tesla vehicle via Fleet API to stop charging. It is an external operation with immediate physical effects on the vehicle. While it can be reversed by restarting charging, the act of stopping a session mid-charge is an active external command execution, not a simple data write. Misuse could interrupt critical charging sessions (e.g., leaving a vehicle with insufficient charge).

From the tool's definition 'Stop charging' — triggers a live command to the vehicle to halt an active charging session

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tesla_charge_stop Rate-limited

tesla_charge_stop stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tesla_charge_stop": {
      "limits": [
        {
          "counter": "tesla_charge_stop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mcp Teslamate Fleet, so you can run agents against it safely.

FAQ

Questions about tesla_charge_stop

What does the tesla_charge_stop tool do? +

Stop charging. 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.

How do I enforce a policy on tesla_charge_stop? +

Register the Mcp Teslamate Fleet MCP server in PolicyLayer and add a rule for tesla_charge_stop: 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.

What risk level is tesla_charge_stop? +

tesla_charge_stop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit tesla_charge_stop? +

Yes. Add a rate_limit block to the tesla_charge_stop 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.

How do I block tesla_charge_stop completely? +

Set action: deny in the PolicyLayer policy for tesla_charge_stop. 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.

What MCP server provides tesla_charge_stop? +

tesla_charge_stop 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.