AI agents call describe_table to retrieve information from MCP Server for Oracle Database without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'describe_table' operation retrieves table structure, column definitions, and constraints—pure data inspection with no side effects. This is a standard Read category tool. While the description is empty, the function name and context (Oracle Database metadata introspection alongside list_tables) make it low-severity information access.
From the tool's definition Tool name 'describe_table' is a standard database introspection operation that retrieves table metadata/schema information. Sibling tool 'list_tables' on the same Oracle server reinforces this as a metadata query function.
Documented attack patterns abuse exactly the kind of access describe_table gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Server for Oracle Database, and nothing reaches the server without passing your rules. This is the rule we recommend for describe_table:
{
"version": "1",
"default": "deny",
"tools": {
"describe_table": {}
}
}describe_table 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.
describe_table. It is categorised as a Read tool in the MCP Server for Oracle Database MCP Server, which means it retrieves data without modifying state.
Register the MCP Server for Oracle Database 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 Server for Oracle Database. 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 Server for Oracle Database MCP server (kutsushitaneko/mcp-server-for-oracle-database). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Server for Oracle Database, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 MCP Server for Oracle Database tools catalogued and risk-classified — across an index of 43,000+ MCP servers.