fitatu_login
AI agents use fitatu_login to create or update resources in Fitatu Wrapper — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fitatu Wrapper environment.
Login operations establish authenticated sessions, which is a state-creating (Write) action. It does not retrieve data, execute code, delete data, or involve finances. Confidence is reduced because the description is empty, but the tool name and server context strongly imply session creation. Severity is medium as misuse could grant unauthorized access to a user's nutrition account.
From the tool's definition Tool name 'fitatu_login' on a server described as enabling 'login, food search, product lookup, daily nutrition read, and adding entries'. Description is empty.
Attacks that exploit this kind of access
fitatu_login. It is categorised as a Write tool in the Fitatu Wrapper MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fitatu Wrapper MCP server in PolicyLayer and add a rule for fitatu_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 Fitatu Wrapper. Nothing to install.
fitatu_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 fitatu_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 fitatu_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.
fitatu_login is provided by the Fitatu Wrapper MCP server (kymylyy/fitatu-wrapper). 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 →