Returns table names, column name and column description of Oracle Database Table Columns
AI agents call get_column_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.
This tool retrieves metadata about database table columns (names, descriptions) without executing queries, modifying data, or triggering side effects. It is a pure read operation used to inform SQL generation. No blast radius from misuse—an AI agent cannot cause harm by requesting column details.
From the tool's definition Tool description states it 'Returns table names, column name and column description' — a retrieval operation with no modification, deletion, or execution of code. The verb 'Returns' and the passive nature of querying metadata indicate data retrieval only.
Documented attack patterns abuse exactly the kind of access get_column_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_column_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_column_details": {}
}
}get_column_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.
Returns table names, column name and column description of Oracle Database Table Columns. 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_column_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_column_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_column_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_column_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_column_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.