list_tables

THE RISK

Low Risk

Why list_tables needs a policy

This tool retrieves schema metadata (table listings) without modifying data or executing arbitrary operations. It is a straightforward read operation that queries database structure information. The server is explicitly designed for read-only access, and listing tables is a non-side-effect query operation. Low severity due to minimal blast radius—at worst, an agent learns the schema structure.

From the tool's definition Tool name 'list_tables' combined with server description stating 'read-only SQL commands and schema inspection tools' and 'provides secure access to table metadata'.

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

POLICY

How to control list_tables

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

policy.json

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

list_tables 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 Db2i — 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 Db2i tools

Read execute_query Execute a read-only SQL SELECT query against the IBM DB2i database. Only SELECT statements Read describe_table Get detailed column information for a specific table including data types, lengths, nullab Read get_table_constraints Get all constraints (primary keys, foreign keys, unique constraints) for a specific table. Read list_indexes List all indexes for a specific table including uniqueness and column information. ${sessi Read list_schemas List all schemas (libraries) in the IBM DB2i database. Optionally filter by name pattern u Read list_views List all views in a schema (library). ${sessionConfig ?

All 7 Db2i 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_tables

What does the list_tables tool do? +

List all tables in a schema (library). ${sessionConfig ?. It is categorised as a Read tool in the Db2i MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_tables? +

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

What risk level is list_tables? +

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

Can I rate-limit list_tables? +

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

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

list_tables is provided by the Db2i MCP server (strom-capital/mcp-server-db2i). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Db2i tool call.

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

CHECK YOUR STACK →