cronometer_search_foods
AI agents call cronometer_search_foods 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 searches or queries food items in Cronometer's database. Search operations are inherently read-only with no side effects or data modification. The empty description prevents full certainty, but the tool name strongly indicates a query/retrieval function typical of nutrition tracking applications.
From the tool's definition Tool name 'cronometer_search_foods' indicates a search operation against food data in Cronometer. The naming convention (search_*) and context within a fitness data access server suggests retrieval without modification.
Attacks that exploit this kind of access
cronometer_search_foods. 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_search_foods: 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_search_foods 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_search_foods 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_search_foods. 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_search_foods 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 →