Send a message
AI agents use sendMessage 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 | — | |
name | string | — | |
seen | boolean | — | |
type | string | — | |
answer | string | — | |
chat_id | number | — | |
content | string | — | |
created | string | — | |
deleted | string | — | |
activity | object | — | |
askACoach | boolean | — | |
end_index | number | — |
Parameters from the server's own tool schema.
Sending a message creates new data (a message record) that can typically be edited or deleted later, making it a Write category tool rather than Execute. The severity is medium because unsolicited or spam messages could disrupt users, but the impact is limited to a single user or conversation thread.
From the tool's definition Tool name 'sendMessage' and description 'Send a message' indicates creation of a new message record in the Intervals.icu system. Messaging is a reversible write operation.
Risk signalsAccepts freeform code/query input (activity.custom_zones[].code) · Accepts file system path (activity.attachments[].filename) · Accepts URL/endpoint input (activity.attachments[].url) · Accepts raw HTML/template content (content) · High parameter count (240 properties)
Attacks that exploit this kind of access
Send a message. 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.
sendMessage accepts 12 parameters: id, name, seen, type, answer, chat_id, content, created, deleted, activity, askACoach, end_index. 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 sendMessage: 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.
sendMessage 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 sendMessage 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 sendMessage. 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.
sendMessage 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 →