Get menstrual data for a specific date
AI agents call get_menstrual_data_for_date to retrieve information from Garmin MCP Server for Poke without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns menstrual tracking data from Garmin Connect for a specified date. It performs a read-only operation that retrieves existing health metrics without creating, modifying, deleting, or executing any code. The verb 'get' confirms data retrieval semantics. While the data is health-sensitive, the tool itself poses minimal risk as it only retrieves information without side effects.
From the tool's definition Tool name 'get_menstrual_data_for_date' and description 'Get menstrual data for a specific date' indicate a retrieval operation with no modification or side effects.
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 for Poke MCP Server, which means it retrieves data without modifying state.
Register the Garmin MCP Server for Poke 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 for Poke. 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 for Poke MCP server (theol0403/garmin-mcp-poke). 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 →