Get a professional cyclist's profile from PCS.
AI agents call get_rider_profile 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 retrieves public professional cycling profile data. It performs no mutations, deletions, financial transactions, or code execution. Even if an AI agent calls it arbitrarily, the worst outcome is redundant data retrieval. The blast radius is negligible.
From the tool's definition Tool description states 'Get a professional cyclist's profile from PCS' — a retrieval operation with no side effects. Sibling tools (discover_races, get_race_overview, get_race_startlist, get_stage_results, search_pcs) are all read-only queries.
Attacks that exploit this kind of access
Get a professional cyclist's profile from PCS. 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_rider_profile: 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_rider_profile 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_rider_profile 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_rider_profile. 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_rider_profile 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 →