get_user_defined_types
AI agents call get_user_defined_types 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 appears to retrieve metadata about user-defined types in the Oracle database schema. This is a passive query operation with no side effects. While the description is empty (reducing confidence), the pattern of 'get_*' sibling tools and typical database introspection patterns suggest this fetches schema information without modifying or executing operations on the database.
From the tool's definition Tool name 'get_user_defined_types' contains the verb 'get', which indicates data retrieval. Description is empty, limiting evidence, but the naming convention aligns with sibling read-only tools like 'get_database_vendor_info', 'get_object_source', and…
Attacks that exploit this kind of access
get_user_defined_types. 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_user_defined_types: 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_user_defined_types 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_user_defined_types 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_user_defined_types. 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_user_defined_types 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 →