get_activities
AI agents call get_activities to retrieve information from Intervals Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves activity records from intervals.icu without modification, deletion, or execution of external operations. The naming convention and context of sibling get_* tools confirm a data retrieval function. No side effects or state changes are implied. Confidence is slightly reduced due to empty tool description, but server context and naming pattern provide strong evidence of read-only behavior.
From the tool's definition Tool name 'get_activities' with sibling tools including 'get_activity_detail', 'get_activity_notes', 'get_athlete', 'get_events', 'get_fitness', and 'get_wellness' all following a consistent read-only retrieval pattern.
Attacks that exploit this kind of access
get_activities. It is categorised as a Read tool in the Intervals Mcp MCP Server, which means it retrieves data without modifying state.
Register the Intervals MCP server in PolicyLayer and add a rule for get_activities: 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 Mcp. Nothing to install.
get_activities 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 get_activities 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 get_activities. 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.
get_activities is provided by the Intervals MCP server (ryansheppard/intervals.mcp). 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 →