Execute a SELECT query to read data from the database.
AI agents call read_query to retrieve information from General-Purpose MCP Database Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs only data retrieval via SELECT statements, which have no side effects on the database state. It does not create, modify, or delete data, making it a Read category tool. Severity is low because the worst case is information disclosure, which is less damaging than Write, Execute, Destructive, or Financial operations.
From the tool's definition Tool name is 'read_query' and description states 'Execute a SELECT query to read data from the database.' SELECT queries retrieve data without modification or deletion.
Attacks that exploit this kind of access
Execute a SELECT query to read data from the database. It is categorised as a Read tool in the General-Purpose MCP Database Server MCP Server, which means it retrieves data without modifying state.
Register the General-Purpose MCP Database Server 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 General-Purpose MCP Database Server. Nothing to install.
read_query 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 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.
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.
read_query is provided by the General-Purpose MCP Database Server MCP server (miekxd/general-database-fastmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →