read_query

Execute a SELECT query.

SERVERCowork Bench SOURCE0717376/cowork_bench

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-bench/read-query.md

WHAT IT DOES

What read_query does on Cowork Bench

AI agents call read_query to retrieve information from Cowork Bench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why read_query is rated Low

The tool executes SELECT queries, which are read-only database operations that retrieve data without modifying it. Severity is medium because SELECT queries could potentially expose sensitive data if misused, but there are no write or destructive side effects.

From the tool's definition Execute a SELECT query

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs read_query safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Cowork Bench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For read_query, this is the rule to start with:

read_query Allowed

read_query is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "read_query": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Cowork Bench, apply this rule, and every read_query call is checked against it from then on.

FAQ

Questions about read_query

What does the read_query tool do? +

Execute a SELECT query. It is categorised as a Read tool in the Cowork Bench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on read_query? +

Register the Cowork Bench MCP server in PolicyLayer and add a rule for read_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 Cowork Bench. Nothing to install.

What risk level is read_query? +

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

Can I rate-limit read_query? +

Yes. Add a rate_limit block to the read_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 read_query completely? +

Set action: deny in the PolicyLayer policy for read_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 read_query? +

read_query is provided by the Cowork Bench MCP server (0717376/cowork_bench). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cowork Bench, and thousands of servers like it.

This server

All 433 Cowork Bench tools →

Across the catalogue

read_input_file on 0gzk →claude_query on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →