cronometer_get_nutrition_scores
AI agents call cronometer_get_nutrition_scores 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.
This tool retrieves nutrition score data from Cronometer without creating, modifying, or deleting any information. The 'get' prefix and sibling read operations confirm this is a data retrieval function with no side effects. Confidence is high despite the empty description because the naming convention and server context are clear. Severity is low as it only exposes personal fitness metrics.
From the tool's definition Tool name 'cronometer_get_nutrition_scores' uses the 'get' verb, indicating data retrieval. The empty description provides no contradictory information.
Attacks that exploit this kind of access
cronometer_get_nutrition_scores. 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 cronometer_get_nutrition_scores: 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.
cronometer_get_nutrition_scores 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 cronometer_get_nutrition_scores 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 cronometer_get_nutrition_scores. 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.
cronometer_get_nutrition_scores 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 →