Get detailed information for a specific activity from Intervals.icu.
AI agents call getActivityDetails to retrieve information from Intervals Icu MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data about a specific activity. It performs a GET-like operation that does not create, modify, delete, or execute code. The action is informational only, making it a Read category risk with low severity since data retrieval poses minimal security risk unless the data itself is highly sensitive (which is not indicated here).
From the tool's definition Tool name 'getActivityDetails' and description 'Get detailed information for a specific activity' indicate a retrieval operation with no modifications or side effects.
Documented attack patterns abuse exactly the kind of access getActivityDetails gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Intervals Icu MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for getActivityDetails:
{
"version": "1",
"default": "deny",
"tools": {
"getActivityDetails": {}
}
} getActivityDetails is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed information for a specific activity from Intervals.icu. It is categorised as a Read tool in the Intervals Icu MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Intervals Icu MCP Server MCP server in PolicyLayer and add a rule for getActivityDetails: 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 MCP Server. Nothing to install.
getActivityDetails 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 getActivityDetails 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 getActivityDetails. 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.
getActivityDetails is provided by the Intervals Icu MCP Server MCP server (mrgeorgegray/intervals-icu-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Intervals Icu MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Intervals Icu MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.