List activities for a date range in desc date order
AI agents call listActivities 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 |
fields | array | — | Comma separated list of field names to include in the returned objects (default is all), also excludes null values |
newest | string | — | Local ISO-8601 date or date and time, defaults to now |
oldest | string | Yes | Local ISO-8601 date or date and time e.g. 2019-07-22T16:18:49 or 2019-07-22 |
route_id | number | — | Only return activities on this route |
Parameters from the server's own tool schema.
This tool retrieves and queries activity data within a specified date range. It has no parameters for modification, deletion, or execution of external operations. The read-only nature and lack of side effects place it squarely in the Read category with low severity.
From the tool's definition Tool name is 'listActivities' and description states 'List activities for a date range in desc date order'. The verb 'List' and the function signature indicate data retrieval only.
Attacks that exploit this kind of access
List activities for a date range in desc date order. It is categorised as a Read tool in the Intervals Icu Api MCP Server, which means it retrieves data without modifying state.
listActivities accepts 6 parameters: id, limit, fields, newest, oldest, route_id. Required: id, oldest. 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 listActivities: 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.
listActivities 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 listActivities 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 listActivities. 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.
listActivities 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 →