Unlock all doors. Requires confirm=True for safety.
AI agents invoke tesla_unlock 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 triggers a physical action on a Tesla vehicle — unlocking all doors. It is an external operation with real-world consequences (vehicle security). While it could be reversed by re-locking, it represents an Execute-category action with high severity since unauthorized unlocking compromises vehicle security and could enable theft or unauthorized access.
From the tool's definition Unlock all doors. Requires confirm=True for safety.
Attacks that exploit this kind of access
Unlock all doors. Requires confirm=True for safety. 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_unlock: 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_unlock 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_unlock 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_unlock. 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_unlock 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 →