Create settings for a sport with default values
AI agents use createSettings 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 | — | |
ftp | number | — | |
lthr | number | — | |
other | boolean | — | |
p_max | number | — | |
types | array | — | |
max_hr | number | — | |
created | string | — | |
display | object | — | |
updated | string | — | |
w_prime | number | — | |
hr_zones | array | — |
Parameters from the server's own tool schema.
This tool creates new settings records for sports, which is a write operation that modifies system configuration state. The action is reversible (settings can typically be updated or deleted later), so it does not qualify as Destructive. The scope appears limited to settings configuration rather than core data, and no financial or code execution is involved.
From the tool's definition Tool name 'createSettings' and description 'Create settings for a sport with default values' indicates creation of configuration data.
Risk signalsHigh parameter count (119 properties)
Attacks that exploit this kind of access
Create settings for a sport with default values. 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.
createSettings accepts 12 parameters: id, ftp, lthr, other, p_max, types, max_hr, created, display, updated, w_prime, hr_zones. 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 createSettings: 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.
createSettings 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 createSettings 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 createSettings. 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.
createSettings 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 →