Get the user
AI agents call get_caloric_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 queries historical caloric data without modifying, deleting, or executing external operations. It follows the read-only pattern of sibling tools (get_active_insights, get_body_progress, get_booking_info). Even if misused, retrieving personal fitness data poses minimal risk compared to destructive or financial operations. Severity is low due to limited blast radius in a personal fitness tracking context.
From the tool's definition Tool name 'get_caloric_history' and prefix 'get_' indicate data retrieval. Description is incomplete ('Get the user') but context shows this is part of a fitness tracking system where get_* tools retrieve user data like workout history, body progress, and…
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_caloric_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_caloric_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_caloric_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_caloric_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_caloric_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 →