list_databases

THE RISK

Low Risk

Why list_databases needs a policy

This tool only queries and retrieves metadata about available databases/schemas without modifying data, executing code, or triggering external operations. It is purely informational with minimal blast radius if misused by an agent.

From the tool's definition Tool name is 'list_databases' and description states it 'List all accessible databases/schemas in the Teradata system.' This is a retrieval operation with no modification or execution of code.

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

POLICY

How to control list_databases

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

policy.json

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

list_databases 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 Tdsql — 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 Tdsql tools

Destructive execute_statement Execute a DDL or DML statement (INSERT, UPDATE, DELETE, CREATE, DROP, etc.). Execute execute_query Execute a SQL SELECT query and return results as JSON. Read describe_table describe_table Read explain_query explain_query Read get_syntax_help get_syntax_help Read list_tables List tables and views in a given database/schema.

All 7 Tdsql 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 list_databases

What does the list_databases tool do? +

List all accessible databases/schemas in the Teradata system. It is categorised as a Read tool in the Tdsql MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_databases? +

Register the Tdsql MCP server in PolicyLayer and add a rule for list_databases: 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 Tdsql. Nothing to install.

What risk level is list_databases? +

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

Can I rate-limit list_databases? +

Yes. Add a rate_limit block to the list_databases 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 list_databases completely? +

Set action: deny in the PolicyLayer policy for list_databases. 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 list_databases? +

list_databases is provided by the Tdsql MCP server (ksturgeon-td/tdsql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Tdsql tool call.

Start from Tdsql, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →