Update a shared event (e.g. race)
AI agents use updateSharedEvent to create or update resources in Intervals Icu Api — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Intervals Icu Api environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes | |
lat | number | — | |
lon | number | — | |
name | string | — | |
owner | object | — | |
types | array | — | |
region | string | — | |
address | string | — | |
body_id | number | — | (body property: id) |
chat_id | number | — | |
country | string | — | |
courses | array | — |
Parameters from the server's own tool schema.
This tool modifies an existing shared event record, which is a Write operation—data is changed but not deleted and can typically be reverted. The severity is medium because a shared event affects potentially multiple users, but the impact is localized to event metadata rather than financial transactions or destructive operations.
From the tool's definition The tool name is 'updateSharedEvent' and the description states it can 'Update a shared event (e.g. race)'. The verb 'update' indicates modification of existing data in a reversible manner.
Risk signalsHigh parameter count (100 properties)
Attacks that exploit this kind of access
Update a shared event (e.g. race). It is categorised as a Write tool in the Intervals Icu Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
updateSharedEvent accepts 12 parameters: id, lat, lon, name, owner, types, region, address, body_id, chat_id, country, courses. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Intervals Icu Api MCP server in PolicyLayer and add a rule for updateSharedEvent: 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.
updateSharedEvent 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 updateSharedEvent 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 updateSharedEvent. 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.
updateSharedEvent 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.
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 →