Find best efforts in the activity
AI agents call findBestEfforts 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 | |
count | number | — | Number of efforts to return |
stream | string | Yes | Stream to search |
distance | number | — | Distance of each effort in meters |
duration | number | — | Duration of each effort in seconds |
endIndex | number | — | Last point in stream to consider (exclusive, default is whole stream) |
minValue | number | — | Minimum average value for each interval, intervals will expand if specified |
startIndex | number | — | First point in stream to consider |
excludeIntervals | boolean | — | If true portions of the stream that are included in work intervals are not considered |
Parameters from the server's own tool schema.
This tool queries and retrieves best effort metrics from an activity without creating, modifying, deleting, or executing external operations. It is a read-only analysis function, making it a Read category risk with low severity since data retrieval poses minimal risk when misused by an AI agent.
From the tool's definition Tool name 'findBestEfforts' and description 'Find best efforts in the activity' indicate a retrieval/query operation that retrieves performance data from an activity.
Attacks that exploit this kind of access
Find best efforts in the activity. It is categorised as a Read tool in the Intervals Icu Api MCP Server, which means it retrieves data without modifying state.
findBestEfforts accepts 9 parameters: id, count, stream, distance, duration, endIndex, minValue, startIndex, excludeIntervals. Required: id, stream. 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 findBestEfforts: 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.
findBestEfforts 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 findBestEfforts 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 findBestEfforts. 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.
findBestEfforts 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 →