get_stage_results
AI agents call get_stage_results to retrieve information from ProCyclingStats MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves historical cycling stage results—a read-only operation with no capacity to modify, delete, or execute external actions. It fits the Read category pattern of fetching sports statistics data. Low severity because misuse by an AI agent would only expose publicly available information without harmful side effects.
From the tool's definition Tool named 'get_stage_results' with context indicating it retrieves stage results data from ProCyclingStats; sibling tools (discover_races, get_race_overview, get_race_startlist, get_rider_profile, search_pcs) are all read-only data queries.
Attacks that exploit this kind of access
get_stage_results. It is categorised as a Read tool in the ProCyclingStats MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ProCyclingStats MCP Server MCP server in PolicyLayer and add a rule for get_stage_results: 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 ProCyclingStats MCP Server. Nothing to install.
get_stage_results 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_stage_results 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_stage_results. 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_stage_results is provided by the ProCyclingStats MCP Server MCP server (lewis-mcgillion/procyclingstats-mcp-server). 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 →