List the user
AI agents call list_my_foods to retrieve information from Iridium 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 or queries nutrition/food data without modifying it. It has no side effects on the data. It falls under the Read category as it queries existing food entries. Severity is low because unauthorized access to personal fitness/nutrition data, while sensitive, does not enable destructive actions, financial transactions, or code execution. An AI misuse would at worst expose personal health information.
From the tool's definition Tool name 'list_my_foods' and description context indicate retrieval of food-related data. The server description states it 'query[s]' workout history, nutrition logs, and body measurements.
Attacks that exploit this kind of access
List the user. It is categorised as a Read tool in the Iridium MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Iridium MCP Server MCP server in PolicyLayer and add a rule for list_my_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 Iridium MCP Server. Nothing to install.
list_my_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 list_my_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 list_my_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.
list_my_foods is provided by the Iridium MCP Server MCP server (rostehea/iridium-mcp-server). 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 →