get_activity_streams
AI agents call get_activity_streams to retrieve information from MCPacer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves activity stream data from Strava (e.g., GPS coordinates, heart rate, power data over time). It performs no mutations, deletions, or external state changes—only queries existing data. Confidence is slightly reduced due to the missing description, but the naming convention and sibling tools provide strong contextual evidence of read-only behavior.
From the tool's definition Tool name 'get_activity_streams' indicates a retrieval operation. Sibling tools follow a consistent pattern: get_* tools (get_activities, get_activities_by_date_range, get_activity_by_id, get_activity_description) are read-only queries of Strava data.
Documented attack patterns abuse exactly the kind of access get_activity_streams gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCPacer, and nothing reaches the server without passing your rules. This is the rule we recommend for get_activity_streams:
{
"version": "1",
"default": "deny",
"tools": {
"get_activity_streams": {}
}
}get_activity_streams 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_activity_streams. It is categorised as a Read tool in the MCPacer MCP Server, which means it retrieves data without modifying state.
Register the MCPacer MCP server in PolicyLayer and add a rule for get_activity_streams: 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 MCPacer. Nothing to install.
get_activity_streams 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_activity_streams 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_activity_streams. 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_activity_streams is provided by the MCPacer MCP server (wernerpe/mcpacer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCPacer, 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.
32 MCPacer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.