tesla_lock · Mcp Teslamate Fleet MCP: Risk & Policy

WHAT IT DOES

What tesla_lock does on Mcp Teslamate Fleet

AI agents invoke tesla_lock 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_lock needs a policy

This tool sends a live command to a Tesla vehicle to lock its doors. While locking is arguably safer than unlocking, it is an external physical operation that affects vehicle state in the real world. It falls under Execute (triggering external operations) rather than Write, as it is a real-time hardware command, not a data modification.

From the tool's definition 'Lock all doors' — triggers a physical vehicle command via the Fleet API that changes the physical state of the vehicle

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tesla_lock Rate-limited

tesla_lock 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_lock": {
      "limits": [
        {
          "counter": "tesla_lock_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_lock

What does the tesla_lock tool do? +

Lock all doors. 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_lock? +

Register the Mcp Teslamate Fleet MCP server in PolicyLayer and add a rule for tesla_lock: 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_lock? +

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

Can I rate-limit tesla_lock? +

Yes. Add a rate_limit block to the tesla_lock 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_lock completely? +

Set action: deny in the PolicyLayer policy for tesla_lock. 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_lock? +

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