AI agents call get-server-version 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 is a simple introspection endpoint that retrieves version information about the server itself. It has no side effects, makes no modifications to data, and poses minimal security risk. Classified as Read with low severity because the information exposed is generally non-sensitive metadata.
From the tool's definition Tool returns server version and metadata with no modification of user data or external state. Name and description clearly indicate a query-only operation.
Attacks that exploit this kind of access
Returns the Strava MCP server version and related metadata. 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 get-server-version: 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.
get-server-version 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-server-version 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-server-version. 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-server-version is provided by the Strava MCP server (@r-huijts/strava-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.