get_routine_folders
AI agents call get_routine_folders to retrieve information from FitnessMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix strongly suggests data retrieval without modification. Given the FitnessMCP context where sibling tools include other 'get_' operations (cronometer_get_daily_nutrition, cronometer_get_fasting_history) that are clearly informational reads, this tool most likely retrieves routine folder metadata. No write, execute, or destructive capabilities are evident from the name.
From the tool's definition Tool name 'get_routine_folders' follows Read pattern (get/retrieve). Description is empty, limiting confidence. Sibling tools show this server performs fitness data access; 'get_' prefix indicates query/retrieval with no side effects.
Attacks that exploit this kind of access
get_routine_folders. It is categorised as a Read tool in the FitnessMCP MCP Server, which means it retrieves data without modifying state.
Register the Fitness MCP server in PolicyLayer and add a rule for get_routine_folders: 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 FitnessMCP. Nothing to install.
get_routine_folders 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_routine_folders 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_routine_folders. 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_routine_folders is provided by the Fitness MCP server (senoj100-alt/fitnessmcp). 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 →