Get table names and description of Oracle Database Tables
AI agents call get_table_details to retrieve information from OracleDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries database schema metadata (table names and descriptions) with no side effects. It does not execute SQL, modify data, delete records, or trigger external operations. This is a standard introspection/discovery capability typical of database clients and poses minimal risk even if invoked by an AI agent, as it only returns informational data about database structure.
From the tool's definition Tool is described as 'Get table names and description of Oracle Database Tables' — it retrieves metadata about tables without modifying or executing operations. This is a read-only query operation.
Documented attack patterns abuse exactly the kind of access get_table_details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OracleDB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_table_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_table_details": {}
}
}get_table_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get table names and description of Oracle Database Tables. It is categorised as a Read tool in the OracleDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OracleDB MCP Server MCP server in PolicyLayer and add a rule for get_table_details: 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 OracleDB MCP Server. Nothing to install.
get_table_details 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_table_details 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_table_details. 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_table_details is provided by the OracleDB MCP Server MCP server (rahgadda/oracledb_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 OracleDB MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
5 OracleDB MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.