This record as markdown: /tools/kh0pper-crow/crow-data-list-saved.md
What crow_data_list_saved does on Crow
AI agents call crow_data_list_saved 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_data_list_saved is rated Low
This tool retrieves and displays stored data (queries, charts, case studies) without altering, deleting, or executing anything. It is a pure read operation with minimal security risk—an AI agent misusing it could only expose information already stored in the system, not cause irreversible harm or external actions.
From the tool's definition Tool name 'list_saved' and description 'List saved queries, charts, and case studies' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs crow_data_list_saved 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_data_list_saved, this is the rule to start with:
crow_data_list_saved 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_data_list_saved call is checked against it from then on.
Questions about crow_data_list_saved
List saved queries, charts, and case studies. 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_data_list_saved: 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_data_list_saved 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_data_list_saved 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_data_list_saved. 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_data_list_saved 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