执行Oracle数据库查询（只读模式）
AI agents call query_oracle to retrieve information from Database Query MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data from Oracle databases without modifying state. The server architecture enforces read-only access and prevents destructive operations. While database queries could theoretically leak sensitive information, the tool itself performs no modifications, executions of external code, financial transactions, or destructive actions. It is purely a data retrieval mechanism.
From the tool's definition Tool name 'query_oracle' with description indicating read-only mode (只读模式). Server description explicitly states 'read-only querying' and 'blocks any data modification operations for safety.' Sibling tools follow the 'query_*' naming pattern consistent with…
Attacks that exploit this kind of access
执行Oracle数据库查询（只读模式）. It is categorised as a Read tool in the Database Query MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Database Query MCP Server MCP server in PolicyLayer and add a rule for query_oracle: 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 Database Query MCP Server. Nothing to install.
query_oracle 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 query_oracle 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 query_oracle. 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.
query_oracle is provided by the Database Query MCP Server MCP server (xuejike/coding-db-mcp). 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 →