Get menstrual cycle calendar data for a date range: cycle phases, predictions, symptoms
AI agents call get_menstrual_calendar_data 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 retrieves existing menstrual cycle data from the user's Garmin Connect account. It performs a read-only operation with no side effects. While the data is sensitive health information, the tool itself cannot modify, delete, or execute any actions — it only fetches data.
From the tool's definition Tool description states 'Get menstrual cycle calendar data' with 'cycle phases, predictions, symptoms' — purely retrieves historical and predictive health data with no modification, deletion, or execution of external operations.
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 Connect, 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 cycle calendar data for a date range: cycle phases, predictions, symptoms. 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_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 Connect. 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 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.