Get COMMUNITY REPAIR STATISTICS from Open Repair Alliance data (300,000+ repair records). USE THIS TOOL WHEN USERS ASK: - "What's the success rate for [device type] repairs?" - "How often do [device type] repairs succeed?" - "What are the most common problems with [device type]?" - "What's the t...
Part of the Sundr Repair Advisor MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_repair_statistics to retrieve information from Sundr Repair Advisor without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_repair_statistics only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_repair_statistics:
rules:
- action: allowSee the full Sundr Repair Advisor policy for all 25 tools.
Agents calling read-class tools like get_repair_statistics have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Get COMMUNITY REPAIR STATISTICS from Open Repair Alliance data (300,000+ repair records). USE THIS TOOL WHEN USERS ASK: - "What's the success rate for [device type] repairs?" - "How often do [device type] repairs succeed?" - "What are the most common problems with [device type]?" - "What's the typical fix rate for [problem]?" - "Are [device type] repairs usually successful?" - "What problems should I expect with my [device]?" - "How likely is repair to work for [issue]?" - "What are common repair barriers for [device]?" - "At what age do [devices] typically fail?" - "Repair success statistics for [category]" COVERS: Smartphones, laptops, tablets, desktop computers, TVs, printers, small kitchen appliances, vacuum cleaners, power tools, headphones, gaming consoles, and more. RETURNS: Fix rates by age and problem type, common failure patterns, repair barriers, and statistical confidence based on sample size.. It is categorised as a Read tool in the Sundr Repair Advisor MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_repair_statistics. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Sundr Repair Advisor MCP server.
get_repair_statistics 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_repair_statistics rule in your Intercept 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 Intercept policy for get_repair_statistics. 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_repair_statistics is provided by the Sundr Repair Advisor MCP server (sundr-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept