Check the status of an async report. Returns status and download URL when complete.
AI agents call vibe.reports.status to retrieve information from Vibe Co MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the status of an existing report and returns metadata (status and download URL). It performs no creation, modification, deletion, or execution of arbitrary code. The operation is purely informational with no side effects, placing it squarely in the Read category. The low severity reflects that checking report status poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'vibe.reports.status' and description 'Check the status of an async report. Returns status and download URL when complete' indicate a read-only query operation that retrieves report metadata without modifying data.
Attacks that exploit this kind of access
Check the status of an async report. Returns status and download URL when complete. It is categorised as a Read tool in the Vibe Co MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Vibe Co MCP Server MCP server in PolicyLayer and add a rule for vibe.reports.status: 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 Vibe Co MCP Server. Nothing to install.
vibe.reports.status 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 vibe.reports.status 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 vibe.reports.status. 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.
vibe.reports.status is provided by the Vibe Co MCP Server MCP server (jacob-hartmann/vibeco-mcp). 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 →