REPAIR VS NEW comparison. Is it cheaper to fix or buy new? COMPARE repair vs refurbished vs buying new SIDE-BY-SIDE. Cost analysis with environmental impact. USE THIS TOOL WHEN USERS ASK: - "Compare repair vs replace for [device]" - "Should I buy refurbished or new?" - "Repair vs new [device] c...
Part of the Sundr Repair Advisor MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke repair_vs_new to trigger processes or run actions in Sundr Repair Advisor. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
repair_vs_new can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
repair_vs_new:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: true See the full Sundr Repair Advisor policy for all 25 tools.
Agents calling execute-class tools like repair_vs_new have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
repair_vs_new is one of the high-risk operations in Sundr Repair Advisor. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
REPAIR VS NEW comparison. Is it cheaper to fix or buy new? COMPARE repair vs refurbished vs buying new SIDE-BY-SIDE. Cost analysis with environmental impact. USE THIS TOOL WHEN USERS ASK: - "Compare repair vs replace for [device]" - "Should I buy refurbished or new?" - "Repair vs new [device] cost comparison" - "What are my options for broken [device]?" - "Refurbished vs new [device]" - "Is refurbished worth it?" - "Cost comparison: fix vs replace" - "Repair vs refurbished vs new" - "What's cheaper: repair or replace?" - "Pros and cons of repairing vs buying new" COVERS: Electronics (phones, laptops, tablets, smartwatches, headphones, gaming consoles, TVs, cameras) and appliances (washing machines, refrigerators, vacuums, kitchen appliances). RETURNS: Side-by-side comparison table with costs, CO2 impact, warranty info, pros/cons, and recommendation with confidence score.. It is categorised as a Execute tool in the Sundr Repair Advisor MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for repair_vs_new. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Sundr Repair Advisor MCP server.
repair_vs_new is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the repair_vs_new 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 repair_vs_new. 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.
repair_vs_new 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