Search the Diabetes:M food database for nutritional information. Returns foods with nutrition per 100g, serving sizes, and source.
AI agents call search_foods to retrieve information from Diabetes:M 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 a food database to retrieve nutritional information. It has no side effects, does not modify data, execute code, delete records, or transfer funds. The narrow scope (food nutrition lookup) and read-only nature pose minimal risk even if misused by an AI agent.
From the tool's definition Tool description states it 'Search[es] the Diabetes:M food database' and 'Returns foods with nutrition' — purely data retrieval with no modification, deletion, or code execution.
Attacks that exploit this kind of access
Search the Diabetes:M food database for nutritional information. Returns foods with nutrition per 100g, serving sizes, and source. It is categorised as a Read tool in the Diabetes:M MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Diabetes:M MCP Server MCP server in PolicyLayer and add a rule for 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 Diabetes:M MCP Server. Nothing to install.
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 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 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.
search_foods is provided by the Diabetes:M MCP Server MCP server (sedoglia/diabetes-m-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 →