fitatu_delete_entry

fitatu_delete_entry

Server Fitatu Wrapper kymylyy/fitatu-wrapper
Category Destructive
Risk class Critical
Parameters 00 required

What fitatu_delete_entry does on Fitatu Wrapper

AI agents call fitatu_delete_entry to permanently remove resources in Fitatu Wrapper — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why fitatu_delete_entry needs a policy

The tool performs a destructive operation (delete) that cannot be undone. Once a nutrition entry is deleted from Fitatu, it is permanently removed from the user's tracking history. This is categorized as Destructive rather than Write because deletion is irreversible. Severity is high because an AI agent misusing this tool could systematically erase a user's nutrition data, disrupting their health tracking goals.

From the tool's definition Tool name 'fitatu_delete_entry' contains the verb 'delete', which indicates irreversible removal of data. The description is empty, preventing detailed verification, but the name alone strongly suggests permanent deletion of nutrition tracking entries.

Questions about fitatu_delete_entry

What does the fitatu_delete_entry tool do? +

fitatu_delete_entry. It is categorised as a Destructive tool in the Fitatu Wrapper MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on fitatu_delete_entry? +

Register the Fitatu Wrapper MCP server in PolicyLayer and add a rule for fitatu_delete_entry: 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.

What risk level is fitatu_delete_entry? +

fitatu_delete_entry is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit fitatu_delete_entry? +

Yes. Add a rate_limit block to the fitatu_delete_entry 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.

How do I block fitatu_delete_entry completely? +

Set action: deny in the PolicyLayer policy for fitatu_delete_entry. 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.

What MCP server provides fitatu_delete_entry? +

fitatu_delete_entry 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.