List activities before and after another activity in closest first order
AI agents call listActivitiesAround to retrieve information from Intervals Icu Api without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | |
limit | number | — | Return at most this many activities (default 30) |
route_id | number | — | Only return activities on this route (activityId must have this route_id) |
activity_id | string | Yes | The activity at the center (not returned in the data set) |
Parameters from the server's own tool schema.
This tool retrieves and lists activities in temporal proximity to another activity. It performs a query/search operation without creating, modifying, deleting, or executing any external operations. The read-only nature and lack of side effects place it firmly in the Read category with low severity.
From the tool's definition Tool name 'listActivitiesAround' and description 'List activities before and after another activity in closest first order' indicate a data retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List activities before and after another activity in closest first order. It is categorised as a Read tool in the Intervals Icu Api MCP Server, which means it retrieves data without modifying state.
listActivitiesAround accepts 4 parameters: id, limit, route_id, activity_id. Required: id, activity_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 listActivitiesAround: 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.
listActivitiesAround is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the listActivitiesAround 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 listActivitiesAround. 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.
listActivitiesAround 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 →