get_pl_sql_objects
AI agents call get_pl_sql_objects 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.
The tool name suggests it retrieves or lists PL/SQL objects (procedures, functions, packages, triggers) from the database schema—a read-only metadata query with no side effects. No evidence suggests data modification, execution, or deletion. The empty description reduces confidence slightly, but contextual consistency with sibling Read tools (get_* pattern) supports classification.
From the tool's definition Tool name 'get_pl_sql_objects' indicates retrieval of PL/SQL object metadata. Description is empty, limiting certainty. Sibling tools like 'get_table_schema', 'get_object_source', and 'get_dependent_objects' are clearly Read operations (schema introspection).
Attacks that exploit this kind of access
get_pl_sql_objects. 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 get_pl_sql_objects: 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.
get_pl_sql_objects 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 get_pl_sql_objects 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 get_pl_sql_objects. 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.
get_pl_sql_objects 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 →