Execute SELECT queries to read data from the oracle database
AI agents call read_query to retrieve information from Oracle MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
SELECT queries are read-only operations that retrieve data without side effects. No data is created, modified, deleted, or financial transactions are executed. The tool is narrowly scoped to query execution, and SELECT statements cannot perform destructive or write operations. Low severity reflects minimal risk of misuse—worst case is unauthorized data access, but no system state is altered.
From the tool's definition Tool name 'read_query' and description 'Execute SELECT queries to read data from the oracle database' explicitly indicate SELECT-only operations with no data modification capability.
Attacks that exploit this kind of access
Execute SELECT queries to read data from the oracle database. It is categorised as a Read tool in the Oracle MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Oracle MCP 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 Oracle MCP 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 Oracle MCP Server MCP server (zhengwanbo/oracle-mcp-server). 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 →