Get a custom item
AI agents call getCustomItem 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 | |
itemId | number | Yes |
Parameters from the server's own tool schema.
The tool retrieves or queries custom item data from the Intervals.icu API with no side effects. The 'Get' verb and lack of any modification language clearly identify this as a Read operation. No data is created, deleted, or overwritten.
From the tool's definition Tool name 'getCustomItem' with description 'Get a custom item' indicates retrieval of data without modification.
Attacks that exploit this kind of access
Get a custom item. It is categorised as a Read tool in the Intervals Icu Api MCP Server, which means it retrieves data without modifying state.
getCustomItem accepts 2 parameters: id, itemId. Required: id, itemId. 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 getCustomItem: 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.
getCustomItem 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 getCustomItem 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 getCustomItem. 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.
getCustomItem 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 →