best_and_worst_results
AI agents call best_and_worst_results to retrieve information from Elections Canada MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve or summarize election results (best and worst performing parties, candidates, or ridings). It matches the pattern of other tools on this server which all perform read-only queries. No side effects, modifications, or irreversible actions are indicated.
From the tool's definition Tool name 'best_and_worst_results' indicates data retrieval. All sibling tools (find_closest_ridings, get_party_votes, get_winning_party, search_ridings, summarize_national_results, summarize_province_results) are Read operations querying election data.
Attacks that exploit this kind of access
best_and_worst_results. It is categorised as a Read tool in the Elections Canada MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Elections Canada MCP Server MCP server in PolicyLayer and add a rule for best_and_worst_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 Elections Canada MCP Server. Nothing to install.
best_and_worst_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 best_and_worst_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 best_and_worst_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.
best_and_worst_results is provided by the Elections Canada MCP Server MCP server (threefortythree-canada/elections-canada-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 →