Authenticate a FeelFit account. If email is omitted and only one account exists, uses that one.
AI agents use login to create or update resources in FeelFit MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FeelFit MCP Server environment.
Login/authentication creates a session or token, which is a state-modifying operation (Write). It doesn't just read data — it establishes credentials/session state on the server. Misuse could allow an agent to authenticate as a user without explicit consent, potentially exposing sensitive health data. Not Execute since it doesn't run arbitrary code, and not Destructive since sessions are reversible.
From the tool's definition Authenticate a FeelFit account
Attacks that exploit this kind of access
Authenticate a FeelFit account. If email is omitted and only one account exists, uses that one. It is categorised as a Write tool in the FeelFit MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FeelFit MCP Server MCP server in PolicyLayer and add a rule for login: 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.
login is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the login 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 login. 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.
login 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 →