Get Body Battery energy levels: charged, drained, highest, lowest. endDate defaults to startDate if omitted
AI agents call get_body_battery to retrieve information from Garmin Connect without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns body battery energy data (charged, drained, highest, lowest levels) without creating, modifying, or deleting any data. It is a straightforward read operation on fitness tracking metrics. No side effects or irreversible actions are possible. Severity is low because exposure of fitness health metrics presents minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_body_battery' and description 'Get Body Battery energy levels' indicate retrieval of fitness/health metrics with no modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access get_body_battery gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Garmin Connect, and nothing reaches the server without passing your rules. This is the rule we recommend for get_body_battery:
{
"version": "1",
"default": "deny",
"tools": {
"get_body_battery": {}
}
}get_body_battery is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get Body Battery energy levels: charged, drained, highest, lowest. endDate defaults to startDate if omitted. It is categorised as a Read tool in the Garmin Connect MCP Server, which means it retrieves data without modifying state.
Register the Garmin Connect MCP server in PolicyLayer and add a rule for get_body_battery: 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 Garmin Connect. Nothing to install.
get_body_battery is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_body_battery 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 get_body_battery. 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.
get_body_battery is provided by the Garmin Connect MCP server (nicolasvegam/garmin-connect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 97 Garmin Connect tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
97 Garmin Connect tools catalogued and risk-classified — across an index of 42,500+ MCP servers.