Create a manual activity
AI agents use createManualActivity 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 | string | Yes | |
gap | number | — | |
feel | number | — | |
gear | object | — | |
lthr | number | — | |
name | string | — | |
pace | number | — | |
race | boolean | — | |
tags | array | — | |
type | string | — | |
group | string | — | |
p_max | number | — |
Parameters from the server's own tool schema.
This tool creates new activity records, which is a reversible write operation. It does not execute code, delete data, or move money. Severity is medium because manual activity creation could inflate training metrics or records if misused by an agent, but the impact is limited to this user's fitness data and is easily corrected by deletion.
From the tool's definition Tool name 'createManualActivity' and description 'Create a manual activity' indicate data creation. The context is Intervals.icu, a fitness/training tracking platform where activities are core data entities.
Risk signalsAccepts freeform code/query input (custom_zones[].code) · Accepts file system path (attachments[].filename) · Accepts URL/endpoint input (attachments[].url) · High parameter count (218 properties)
Attacks that exploit this kind of access
Create a manual activity. 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.
createManualActivity accepts 12 parameters: id, gap, feel, gear, lthr, name, pace, race, tags, type, group, p_max. 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 createManualActivity: 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.
createManualActivity 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 createManualActivity 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 createManualActivity. 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.
createManualActivity 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 →