intervals_bulk_delete_events
AI agents call intervals_bulk_delete_events to permanently remove resources in FitnessMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Bulk deletion operations are classified as Destructive because they permanently and irreversibly remove data. Even though the description is empty, the tool name is unambiguous: 'delete' is a clear destructive verb applied to 'events' in bulk. The high confidence reflects the explicit language in the tool name, despite lack of descriptive detail.
From the tool's definition Tool name contains 'bulk_delete_events' which explicitly indicates irreversible deletion of multiple records. The 'delete' operation combined with 'bulk' scope indicates data that cannot be undone.
Attacks that exploit this kind of access
intervals_bulk_delete_events. It is categorised as a Destructive tool in the FitnessMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Fitness MCP server in PolicyLayer and add a rule for intervals_bulk_delete_events: 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 FitnessMCP. Nothing to install.
intervals_bulk_delete_events 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 intervals_bulk_delete_events 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 intervals_bulk_delete_events. 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.
intervals_bulk_delete_events is provided by the Fitness MCP server (senoj100-alt/fitnessmcp). 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 →