Get kudoers for a specific activity
AI agents call getActivityKudoers to retrieve information from Strava without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a list of users who have given kudos (likes) to a specific Strava activity. It queries existing data without creating, modifying, deleting, or executing any operations. The data returned is informational and read-only, with no side effects or ability to affect Strava's state or user accounts. Blast radius is minimal—misuse would only expose publicly available social engagement data.
From the tool's definition Tool name 'getActivityKudoers' and description 'Get kudoers for a specific activity' indicate a retrieval operation. The verb 'Get' and absence of any modification, deletion, or execution language confirm this is a read-only query.
Documented attack patterns abuse exactly the kind of access getActivityKudoers gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Strava, and nothing reaches the server without passing your rules. This is the rule we recommend for getActivityKudoers:
{
"version": "1",
"default": "deny",
"tools": {
"getActivityKudoers": {}
}
}getActivityKudoers 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 kudoers for a specific activity. It is categorised as a Read tool in the Strava MCP Server, which means it retrieves data without modifying state.
Register the Strava MCP server in PolicyLayer and add a rule for getActivityKudoers: 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 Strava. Nothing to install.
getActivityKudoers 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 getActivityKudoers 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 getActivityKudoers. 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.
getActivityKudoers is provided by the Strava MCP server (kw510/strava-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Strava, 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.
37 Strava tools catalogued and risk-classified — across an index of 43,000+ MCP servers.