Set cabin temperature target (Fahrenheit). Both driver and passenger.
AI agents invoke tesla_set_temp 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 physical vehicle to change its climate control settings. It triggers an external operation (modifying vehicle HVAC state) rather than simply reading or writing data in a database. While it is reversible (temperature can be changed again), it constitutes executing a remote command on a physical device.
From the tool's definition Set cabin temperature target (Fahrenheit). Both driver and passenger.
Attacks that exploit this kind of access
Set cabin temperature target (Fahrenheit). Both driver and passenger. 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_set_temp: 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_set_temp 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_set_temp 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_set_temp. 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_set_temp 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 →