Get health goals for a FeelFit account.
AI agents call get_goals to retrieve information from FeelFit 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 stored health goal information without creating, modifying, deleting, or executing any operations. It has no blast radius beyond potential exposure of personal health data, which is a privacy concern but not a functional security risk. The severity is low because misuse by an AI agent would only allow unauthorized data access, not modification or destructive actions.
From the tool's definition Tool name 'get_goals' and description 'Get health goals for a FeelFit account' indicate a retrieval operation with no side effects. The verb 'Get' and context of reading health goal data from the FeelFit Cloud API confirm this is a read-only operation.
Attacks that exploit this kind of access
Get health goals for a FeelFit account. It is categorised as a Read tool in the FeelFit MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FeelFit MCP Server MCP server in PolicyLayer and add a rule for get_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 FeelFit MCP Server. Nothing to install.
get_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_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_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_goals is provided by the FeelFit MCP Server MCP server (tecnologicachile/mcp-feelfit). 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 →