Retrieve source code of a PL/SQL object or VIEW definition.
AI agents call oracle_get_source 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.
This tool queries and returns existing metadata (source code of PL/SQL objects and VIEW definitions) without altering database state. It is a straightforward retrieval operation analogous to a SELECT or DESCRIBE query. While the source code retrieved might reveal sensitive logic, the tool itself performs no destructive, executable, or modifying actions.
From the tool's definition Tool description explicitly states 'Retrieve source code' of database objects. The verb 'retrieve' and absence of modification keywords (create, update, delete, execute) indicate a read-only operation. No side effects or state changes are implied.
Attacks that exploit this kind of access
Retrieve source code of a PL/SQL object or VIEW definition. 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_get_source: 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_get_source 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_get_source 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_get_source. 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_get_source 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 →