Get the user
AI agents call get_cycle_history to retrieve information from Arvo 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 cycle data (likely training cycles or menstrual cycles in a fitness context) for the user. It performs data retrieval without modifying, deleting, or executing operations. The low severity reflects minimal blast radius—exposure of workout cycle history is a privacy concern but not immediately harmful.
From the tool's definition Tool name includes 'get_' prefix indicating retrieval operation; function is to fetch cycle history data for the user, which is a read-only query with no modification or side effects.
Attacks that exploit this kind of access
Get the user. It is categorised as a Read tool in the Arvo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Arvo MCP Server MCP server in PolicyLayer and add a rule for get_cycle_history: 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 Arvo MCP Server. Nothing to install.
get_cycle_history 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_cycle_history 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_cycle_history. 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_cycle_history is provided by the Arvo MCP Server MCP server (khaoss85/arvo-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 →