Get menstrual data for a specific date
AI agents call get_menstrual_data_for_date 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 historical menstrual cycle data from Garmin Connect for a specified date. It performs no write, delete, or execute operations — no data is modified, created, or destroyed. The blast radius of misuse is minimal (unauthorized access to sensitive personal health data), making it a Read operation with low severity despite the intimate nature of the data being retrieved.
From the tool's definition Tool name is 'get_menstrual_data_for_date' and description states 'Get menstrual data for a specific date' — the verb 'get' indicates data retrieval without modification.
Attacks that exploit this kind of access
Get menstrual data for a specific date. 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_data_for_date: 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_data_for_date 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_data_for_date 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_data_for_date. 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_data_for_date is provided by the Garmin MCP Server MCP server (jbaker48/garmin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →