search_competitions
AI agents call search_competitions to retrieve information from Unofficial WCA 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 or queries competition information from the WCA database without modifying, deleting, or executing external operations. It has no side effects and falls squarely within the Read category. Low severity due to public nature of WCA speedcubing data.
From the tool's definition Tool name 'search_competitions' and sibling tools (get_competition_by_id, get_competition_results, get_records, get_person_by_wca_id, get_wca_countries, search_persons) all follow a retrieval/query pattern.
Attacks that exploit this kind of access
search_competitions. It is categorised as a Read tool in the Unofficial WCA MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Unofficial WCA MCP Server MCP server in PolicyLayer and add a rule for search_competitions: 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 Unofficial WCA MCP Server. Nothing to install.
search_competitions 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 search_competitions 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 search_competitions. 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.
search_competitions is provided by the Unofficial WCA MCP Server MCP server (yuchengmautk/unofficial-wca-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 →