Remove a previously logged exercise by its logId (from log_activity output or from get_exercise_list[].logId).
AI agents call delete_activity_log to permanently remove resources in Fitbit Googlehealth — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes user health data (activity/exercise logs). Although not financial in nature, deletion of historical health records constitutes destructive data loss with potential consequences for health tracking, medical records, and user autonomy. The blast radius is high because a misbehaving agent could erase a user's entire exercise history.
From the tool's definition Tool name 'delete_activity_log' explicitly performs deletion of exercise logs irreversibly. Description states 'Remove a previously logged exercise by its logId', confirming the action cannot be undone.
Attacks that exploit this kind of access
Remove a previously logged exercise by its logId (from log_activity output or from get_exercise_list[].logId). It is categorised as a Destructive tool in the Fitbit Googlehealth MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Fitbit Googlehealth MCP server in PolicyLayer and add a rule for delete_activity_log: 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 Fitbit Googlehealth. Nothing to install.
delete_activity_log is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_activity_log 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 delete_activity_log. 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.
delete_activity_log is provided by the Fitbit Googlehealth MCP server (tachibanayu24/fitbit-googlehealth-mcp). 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 →