describe_table

Describe a table structure.

SERVERMulti-DB MCP Server SOURCE1249zts/db-mcp-service

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/1249zts-db-mcp-service/describe-table.md

WHAT IT DOES

What describe_table does on Multi-DB MCP Server

AI agents call describe_table to retrieve information from Multi-DB MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why describe_table is rated Low

This tool retrieves metadata about a table's schema (columns, types, constraints, etc.) without executing queries, modifying data, or triggering side effects. It is a read-only information lookup operation, analogous to DESCRIBE or SHOW COLUMNS commands in SQL. While the server supports SQL execution via sibling tools, this specific tool is narrowly scoped to non-destructive schema inspection.

From the tool's definition Tool name is 'describe_table' and description states it 'Describe[s] a table structure' — a retrieval operation with no modification or execution of arbitrary code.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs describe_table safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Multi-DB MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For describe_table, this is the rule to start with:

describe_table Allowed

describe_table is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "describe_table": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Multi-DB MCP Server, apply this rule, and every describe_table call is checked against it from then on.

FAQ

Questions about describe_table

What does the describe_table tool do? +

Describe a table structure. It is categorised as a Read tool in the Multi-DB MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on describe_table? +

Register the Multi-DB MCP Server 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 Multi-DB MCP Server. Nothing to install.

What risk level is describe_table? +

describe_table is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit describe_table? +

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.

How do I block describe_table completely? +

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.

What MCP server provides describe_table? +

describe_table is provided by the Multi-DB MCP Server MCP server (1249zts/db-mcp-service). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Multi-DB MCP Server, and thousands of servers like it.

This server

All 5 Multi-DB MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →