# The nine tools your agent can call

> What each of Rabbot's nine MCP tools answers, and the one tool that can change anything.
> Category: Agent access (MCP)
> Canonical: https://rabbot.ai/docs/mcp/the-nine-tools/
> Updated: 2026-08-24

---

Rabbot's MCP server holds nine tools bound to one store at a time. Eight only read; one writes, and it refuses on anything that would matter if it went wrong.

## The eight read tools

- `get_protection_status` returns your plan, how many monitored URLs you are using against your cap, when the last full check ran, and how many open issues sit at each severity.
- `whats_blocking_sales` returns what is stopping a sale right now, grouped into product stories with a chip for the channel involved, rather than a flat list of rows.
- `list_open_issues` returns every open problem, most severe first, with the page, the rule it tripped, the severity, the detail, and when it opened.
- `get_url_timeline` returns one page's history, newest first: changes, when an issue opened, when it was fixed, and clean runs in between. Seven days back on the free plan, the full history on paid plans.
- `list_recent_catches` returns what Rabbot caught and confirmed fixed in the last 30 days. Use it when someone asks what Rabbot has actually caught.
- `get_url_health` returns one monitored URL's last check time, what that check found, and its open issues.
- `list_day0_findings` returns the audit Rabbot ran the day it was installed: price, availability, status, and completeness findings from your feed at that point.
- `notifications_sent` returns what actually went out in the last seven days, by channel, straight from the send log, so you can check an alert really was sent before you go looking for it elsewhere.

## The one write tool

- `dismiss_finding` marks a finding as intentional, for one page or store-wide, so Rabbot stops flagging it. It refuses on anything blocking a sale, with two documented exceptions that can be intentional: a deliberate password gate or a custom purchase flow. Everything else in that category cannot be silenced by an agent, only fixed. Dismissing a finding mutes the alert; it does not fake a fix. If the underlying problem is later repaired, the finding closes and the dismissal goes with it. If it comes back after that, Rabbot alerts again as normal.

## Asking for these in plain language

You do not need to know the tool names to use them. Ask your agent a plain question, "what's blocking sales" or "show me this page's history", and it picks the right tool on its own. The names above are here so you know what exists and what each one is bound to answer, not because you need to type them yourself.