Return column metadata for SCHEMA.TABLE.
AI agents call describe_table to retrieve information from Mcp Oracle Dba 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 table columns—structure information without querying data or modifying anything. It has no side effects and fits the Read category. Severity is low because metadata exposure alone has minimal blast radius unless the database contains highly sensitive schema information, but the audited and guarded server design mitigates this.
From the tool's definition Tool name 'describe_table' and description 'Return column metadata for SCHEMA.TABLE' indicate retrieval of table structure information only. Server description emphasizes 'read-only' and 'SQL-guarded' design.
Attacks that exploit this kind of access
Return column metadata for SCHEMA.TABLE. It is categorised as a Read tool in the Mcp Oracle Dba MCP Server, which means it retrieves data without modifying state.
Register the Mcp Oracle Dba MCP server in PolicyLayer and add a rule for describe_table: 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 Mcp Oracle Dba. Nothing to install.
describe_table 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 describe_table 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 describe_table. 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.
describe_table is provided by the Mcp Oracle Dba MCP server (shopsmartai/mcp-oracle-dba). 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 →