crow_actual_reports
Generate a spending summary report. Groups transactions by category, payee, or month.
This record as markdown: /tools/kh0pper-crow/crow-actual-reports.md
What crow_actual_reports does on Crow
AI agents call crow_actual_reports to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why crow_actual_reports is rated Low
This tool queries and aggregates financial transaction data for reporting purposes, characteristic of a Read operation. While it deals with financial data, it does not move money, commit financial obligations, modify records, or delete data. The blast radius of misuse is limited to unauthorized visibility into spending patterns; no financial transactions or data destruction can occur through this tool.
From the tool's definition Tool performs 'Generate a spending summary report' that 'Groups transactions by category, payee, or month' — explicitly a read/retrieval operation that summarizes and organizes existing data without modification.
Attacks that exploit this kind of access
The rule that runs crow_actual_reports safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_actual_reports, this is the rule to start with:
crow_actual_reports 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 Crow, apply this rule, and every crow_actual_reports call is checked against it from then on.
Questions about crow_actual_reports
Generate a spending summary report. Groups transactions by category, payee, or month. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for crow_actual_reports: 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 Crow. Nothing to install.
crow_actual_reports 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 crow_actual_reports 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 crow_actual_reports. 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.
crow_actual_reports is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
This server
Across the catalogue