read-query

THE RISK

Low Risk

Why read-query needs a policy

This tool is classified as Read because it executes SELECT queries, which retrieve data without side effects. The description emphasizes security validation, further supporting safe data retrieval. The presence of sibling destructive tools (alter-table, create-table, write-query) on the same server confirms this tool is scoped to read-only operations.

From the tool's definition Tool name 'read-query' and description 'Execute SELECT queries' explicitly indicates retrieval operations only. SELECT queries do not modify, delete, or execute arbitrary code.

Documented attack patterns abuse exactly the kind of access read-query gives an agent:

POLICY

How to control read-query

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "read-query": {}
  }
}

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

Create a free account and register Mcp Libsql — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Mcp Libsql tools

Destructive alter-table Table structure modifications (ADD/RENAME/DROP operations) Write create-table DDL operations for table creation with security measures Write write-query INSERT/UPDATE/DELETE operations with transaction support Read describe-table Table schema inspection with multiple output formats Read list-tables Database metadata browsing with filtering options

All 6 Mcp Libsql tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about read-query

What does the read-query tool do? +

Execute SELECT queries with comprehensive security validation. It is categorised as a Read tool in the Mcp Libsql MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on read-query? +

Register the Mcp Libsql 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 Mcp Libsql. 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 Mcp Libsql MCP server (xexr/mcp-libsql). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Libsql tool call.

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

CHECK YOUR STACK →