tesla_charging_history

Charging sessions over the last N days.

Server Mcp Teslamate Fleet lodordev/mcp-teslamate-fleet
Category Read
Risk class Low
Parameters 00 required

What tesla_charging_history does on Mcp Teslamate Fleet

AI agents call tesla_charging_history to retrieve information from Mcp Teslamate Fleet without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why tesla_charging_history needs a policy

This tool queries historical analytics data (charging sessions) from TeslaMate. It is a read-only operation that fetches past records over a specified time window, with no ability to modify, execute, or delete anything.

From the tool's definition Charging sessions over the last N days — retrieves historical charging session data with no side effects.

Questions about tesla_charging_history

What does the tesla_charging_history tool do? +

Charging sessions over the last N days. It is categorised as a Read tool in the Mcp Teslamate Fleet MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on tesla_charging_history? +

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

tesla_charging_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit tesla_charging_history? +

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

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.