Low Risk

crow_data_query

Execute a read-only SQL query on a user-owned SQLite database. Only SELECT, EXPLAIN, PRAGMA, and WITH are allowed. Max 5000 rows, 10s timeout.

How to control crow_data_query ↓

What crow_data_query does on Crow

AI agents call crow_data_query to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why crow_data_query needs a policy

The tool is explicitly restricted to read-only operations (SELECT, EXPLAIN, PRAGMA, WITH). It cannot modify, delete, or execute arbitrary code. The database is user-owned, and the 5000-row and 10-second limits further constrain potential impact. This is a data retrieval tool with no side effects.

From the tool's definition Execute a read-only SQL query on a user-owned SQLite database. Only SELECT, EXPLAIN, PRAGMA, and WITH are allowed.

Documented attack patterns abuse exactly the kind of access crow_data_query gives an agent:

How to control crow_data_query

PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crow_data_query:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "crow_data_query": {}
  }
}

crow_data_query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Crow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about crow_data_query

What does the crow_data_query tool do? +

Execute a read-only SQL query on a user-owned SQLite database. Only SELECT, EXPLAIN, PRAGMA, and WITH are allowed. Max 5000 rows, 10s timeout. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on crow_data_query? +

Register the Crow MCP server in PolicyLayer and add a rule for crow_data_query: 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.

What risk level is crow_data_query? +

crow_data_query is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit crow_data_query? +

Yes. Add a rate_limit block to the crow_data_query 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.

How do I block crow_data_query completely? +

Set action: deny in the PolicyLayer policy for crow_data_query. 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.

What MCP server provides crow_data_query? +

crow_data_query 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.

Enforce policy on every Crow tool call.

Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.