list_advisor_findings
Browse the ADVISOR CENTER findings (public.advisor_findings) — the advisor-monitor's deduped audit/health findings you see on the dashboard /advisor view. Filter by severity (info|warning|alert), kind (a taxonomy slug like audit.denied_spike / advisor.security), and q (free-text over the finding ...
This record as markdown: /tools/dev-busymate-busymate-devtools/list-advisor-findings.md
What list_advisor_findings does on Busymate DevTools
AI agents call list_advisor_findings to retrieve information from Busymate DevTools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | — | Free-text substring over the finding title + kind + fingerprint. |
kind | string | — | Filter by taxonomy kind slug (e.g. audit.denied_spike, advisor.security). |
limit | number | — | Max rows (default 50, cap 200). |
before | string | — | Keyset cursor — the previous page's last last_seen_at (from next_cursor). |
severity | string | — | Filter by severity. |
Parameters from the server's own tool schema.
Why list_advisor_findings is rated Low
This tool retrieves and filters existing findings data from a dashboard view with no data modification, creation, deletion, or execution of external operations. It performs read-only queries with filtering and pagination capabilities. The gating by 'audit:view' permission further confirms it is a read operation.
From the tool's definition Browse the ADVISOR CENTER findings (public.advisor_findings)...Filter by...keyset-paginate...Each row: fingerprint, kind, severity, first_seen_at, last_seen_at, times_seen, analysis {title,body,suggestion,fix}, filters, sample_event_ids. Gated audit:view.
Attacks that exploit this kind of access
The rule that runs list_advisor_findings safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Busymate DevTools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_advisor_findings, this is the rule to start with:
list_advisor_findings is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Busymate DevTools, apply this rule, and every list_advisor_findings call is checked against it from then on.
Questions about list_advisor_findings
Browse the ADVISOR CENTER findings (public.advisor_findings) — the advisor-monitor's deduped audit/health findings you see on the dashboard /advisor view. Filter by severity (info|warning|alert), kind (a taxonomy slug like audit.denied_spike / advisor.security), and q (free-text over the finding title + kind + fingerprint). Newest-first (last_seen_at); keyset-paginate by passing the returned next_cursor as before. Each row: fingerprint, kind, severity, first_seen_at, last_seen_at, times_seen, analysis {title,body,suggestion,fix}, filters, sample_event_ids. Gated audit:view. It is categorised as a Read tool in the Busymate DevTools MCP Server, which means it retrieves data without modifying state.
list_advisor_findings accepts 5 parameters: q, kind, limit, before, severity. The full parameter table on this page comes from the server's own tool schema.
Register the Busymate DevTools MCP server in PolicyLayer and add a rule for list_advisor_findings: 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 Busymate DevTools. Nothing to install.
list_advisor_findings 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 list_advisor_findings 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 list_advisor_findings. 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.
list_advisor_findings is provided by the Busymate DevTools MCP server (https://mcp.busymate.dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Busymate DevTools, and thousands of servers like it.
This server
Across the catalogue