get_related_tables
AI agents call get_related_tables 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.
Although the description is empty (lowering confidence from 0.85 to 0.75), the tool name and position among other introspection tools clearly indicate it retrieves relationship metadata about tables—a Read operation with no side effects. Low severity because it only accesses schema information, not sensitive data operations.
From the tool's definition Tool name 'get_related_tables' with no description suggests a query/retrieval operation. Contextual clues: sibling tools include exec_ddl_sql, exec_dml_sql (Execute/Destructive), but this tool follows the pattern of other Read tools like get_table_schema,…
Attacks that exploit this kind of access
get_related_tables. 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_related_tables: 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_related_tables 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_related_tables 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_related_tables. 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_related_tables 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 →