Get stats and body composition data Args: date: Date in YYYY-MM-DD format
AI agents call get_stats_and_body 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 retrieves fitness and health statistics and body composition information from Garmin Connect without modifying, deleting, or executing any operations. It is a straightforward data query with no side effects. While body composition data is personal health information, the risk is limited to unauthorized reading rather than modification or destruction.
From the tool's definition Tool name 'get_stats_and_body' and description 'Get stats and body composition data' indicate retrieval only. The arg is a date filter for querying existing data. No mutation, deletion, or execution verbs are present.
Documented attack patterns abuse exactly the kind of access get_stats_and_body 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_stats_and_body:
{
"version": "1",
"default": "deny",
"tools": {
"get_stats_and_body": {}
}
}get_stats_and_body 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 stats and body composition data Args: date: 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_stats_and_body: 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_stats_and_body 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_stats_and_body 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_stats_and_body. 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_stats_and_body 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.