Get menstrual calendar data between specified dates Automatically chunks requests longer than 92 days, Garmin's server-side limit, and stitches the responses together. Args: start_date: Start date in YYYY-MM-DD format end_date: End date in YYYY-MM-DD format
AI agents call get_menstrual_calendar_data 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 queries and retrieves health data (menstrual calendar information) without modifying, deleting, or executing operations. While the data retrieved is sensitive personal health information that could warrant a medium severity rating due to privacy implications if misused by an agent to access or expose intimate health details, the tool itself performs only a read operation.
From the tool's definition Tool retrieves menstrual calendar data with 'Get' action and date range parameters; no modification, deletion, or execution of external operations. Description explicitly states it 'Get[s]' data and 'stitches responses together' without side effects.
Documented attack patterns abuse exactly the kind of access get_menstrual_calendar_data 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_menstrual_calendar_data:
{
"version": "1",
"default": "deny",
"tools": {
"get_menstrual_calendar_data": {}
}
}get_menstrual_calendar_data 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 menstrual calendar data between specified dates Automatically chunks requests longer than 92 days, Garmin's server-side limit, and stitches the responses together. 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_menstrual_calendar_data: 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_menstrual_calendar_data 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_menstrual_calendar_data 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_menstrual_calendar_data. 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_menstrual_calendar_data 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.