describe_table

THE RISK

Low Risk

Why describe_table needs a policy

This tool retrieves table schema information (columns, types, constraints, etc.) with no side effects. It is a read-only operation analogous to DESCRIBE or SHOW COLUMNS in SQL. No data is created, modified, deleted, or executed; it merely queries structural metadata. Even if misused by an AI agent, the blast radius is minimal—only information disclosure of schema design.

From the tool's definition Tool name 'describe_table' and description 'Get table structure' indicate a retrieval operation that inspects schema metadata without modifying or executing code against data.

Documented attack patterns abuse exactly the kind of access describe_table gives an agent:

POLICY

How to control describe_table

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-MongoDB-MySQL-Server, and nothing reaches the server without passing your rules. This is the rule we recommend for describe_table:

policy.json

{
  "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.

Create a free account and register MCP-MongoDB-MySQL-Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP-MongoDB-MySQL-Server tools

Destructive mongodb_delete Delete documents from a MongoDB collection Execute execute Execute an INSERT, UPDATE, or DELETE query Execute connect_mongodb Connect to MongoDB database using URL or config Write add_column Add a new column to existing table Write create_table Create a new table in the database Write mongodb_create_collection Create a new collection in MongoDB Write mongodb_insert Insert documents into a MongoDB collection Write mongodb_update Update documents in a MongoDB collection

All 14 MCP-MongoDB-MySQL-Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about describe_table

What does the describe_table tool do? +

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

How do I enforce a policy on describe_table? +

Register the MCP-MongoDB-MySQL-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 MCP-MongoDB-MySQL-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 MCP-MongoDB-MySQL-Server MCP server (yaoxiaolinglong/mcp-mongodb-mysql-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP-MongoDB-MySQL-Server tool call.

Start from MCP-MongoDB-MySQL-Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →