crow_list_backends
List registered data backends with their connection status.
This record as markdown: /tools/kh0pper-crow/crow-list-backends.md
What crow_list_backends does on Crow
AI agents call crow_list_backends 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_list_backends is rated Low
This tool performs a read-only operation that queries and returns data about backend systems without modifying, deleting, or executing any operations. The action of listing and checking connection status has no side effects on the backends themselves or the data they manage. The severity is low as the blast radius of misuse is limited to information disclosure about backend infrastructure.
From the tool's definition Tool name 'list_backends' and description 'List registered data backends with their connection status' indicate a query operation that retrieves information about existing backend configurations and their states.
Attacks that exploit this kind of access
The rule that runs crow_list_backends 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_list_backends, this is the rule to start with:
crow_list_backends 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_list_backends call is checked against it from then on.
Questions about crow_list_backends
List registered data backends with their connection status. 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_list_backends: 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_list_backends 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_list_backends 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_list_backends. 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_list_backends 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