deleteSharedEvent

Delete a shared event (e.g. race)

Server Intervals Icu Api intervals-icu-api-mcp-server
Category Destructive
Risk class Critical
Parameters 11 required

What deleteSharedEvent does on Intervals Icu Api

AI agents call deleteSharedEvent to permanently remove resources in Intervals Icu Api — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

ParameterTypeRequiredDescription
id number Yes

Parameters from the server's own tool schema.

Why deleteSharedEvent needs a policy

This tool permanently removes a shared event from the system with no indication of undo capability. Shared events (e.g., races) may be referenced by multiple users or activities, making unintended deletion a high-severity risk. The Destructive category applies because the action cannot be reversed and has potential impact on other users who depend on the shared event.

From the tool's definition Tool name contains 'delete' and description states 'Delete a shared event'. The verb 'delete' combined with 'shared event' indicates irreversible removal of data.

Questions about deleteSharedEvent

What does the deleteSharedEvent tool do? +

Delete a shared event (e.g. race). It is categorised as a Destructive tool in the Intervals Icu Api MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does deleteSharedEvent accept? +

deleteSharedEvent accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on deleteSharedEvent? +

Register the Intervals Icu Api MCP server in PolicyLayer and add a rule for deleteSharedEvent: 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 Intervals Icu Api. Nothing to install.

What risk level is deleteSharedEvent? +

deleteSharedEvent 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 deleteSharedEvent? +

Yes. Add a rate_limit block to the deleteSharedEvent 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 deleteSharedEvent completely? +

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

deleteSharedEvent is provided by the Intervals Icu Api MCP server (intervals-icu-api-mcp-server). 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.