Get body battery data with events Args: start_date: Start date in YYYY-MM-DD format end_date: End date in YYYY-MM-DD format
AI agents call get_body_battery to retrieve information from Garmin MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read operation that queries and retrieves personal fitness/health data from Garmin Connect. It has no side effects, does not modify any data, and does not execute external operations. While it accesses personal health information which may be sensitive, the impact of misuse is limited to unauthorized data access rather than modification or destruction.
From the tool's definition get_body_battery retrieves body battery data with events within a specified date range. It takes start_date and end_date parameters and returns existing data without modification.
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 MCP Server, 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 data with events Args: start_date: Start date in YYYY-MM-DD format end_date: End date in YYYY-MM-DD format. It is categorised as a Read tool in the Garmin MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Garmin MCP Server 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 MCP Server. 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 MCP Server MCP server (taxuspt/garmin_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 126 Garmin MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
126 Garmin MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.