Search for database objects by name pattern, or search within PL/SQL source code.
AI agents call oracle_search to retrieve information from Oracle APEX MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs database object discovery and source code inspection. These are read-only operations that retrieve information without side effects, reversible modifications, code execution, or data destruction. The blast radius is minimal — search results cannot directly alter system state or trigger unintended operations.
From the tool's definition Tool description states 'Search for database objects by name pattern, or search within PL/SQL source code' — both are query/search operations with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
Search for database objects by name pattern, or search within PL/SQL source code. It is categorised as a Read tool in the Oracle APEX MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Oracle APEX MCP Server MCP server in PolicyLayer and add a rule for oracle_search: 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 APEX MCP Server. Nothing to install.
oracle_search 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 oracle_search 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 oracle_search. 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.
oracle_search is provided by the Oracle APEX MCP Server MCP server (silviosotelo/oracle-apex-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 →