Get the user
AI agents call get_nutrition_goals 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 queries and retrieves user nutrition goal information from the Iridium fitness platform. It performs a read-only operation with no side effects, data modification, code execution, or destructive capability. The risk is low because exposure of nutrition goals data to an AI agent represents minimal security risk compared to write or destructive operations.
From the tool's definition Tool name is 'get_nutrition_goals' and sibling tools are all 'get_*' functions that retrieve data (get_body_measurements, get_exercise_progress, get_food_entries, get_nutrition_log, get_personal_records, get_profile, get_trainer_analysis,…
Attacks that exploit this kind of access
Get 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 get_nutrition_goals: 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.
get_nutrition_goals 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_nutrition_goals 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_nutrition_goals. 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_nutrition_goals 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 →