podbc_filter_table_names

THE RISK

Low Risk

Why podbc_filter_table_names needs a policy

This tool queries database metadata (table names/schemas) and returns results without side effects. It is purely informational retrieval, matching the Read category definition. Severity is low because it only exposes table metadata that an attacker could discover through other database introspection methods, with no capability to modify data, execute queries, or cause harm.

From the tool's definition Tool description states 'Retrieve and return a list containing information about tables whose names contain the substring' — a read-only query operation that returns metadata about tables. No modification, deletion, or execution of arbitrary code is described.

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

POLICY

How to control podbc_filter_table_names

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

policy.json

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

podbc_filter_table_names 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 Sqlalchemy — 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 Sqlalchemy tools

Execute podbc_execute_query Execute a SQL query and return results in JSONL format. Execute podbc_execute_query_md Execute a SQL query and return results in Markdown table format. Execute podbc_query_database Execute a SQL query and return results in JSONL format. Execute podbc_sparql_func Tool to use the SPARQL AI support function Execute podbc_spasql_query Execute a SPASQL query and return results. Execute podbc_virtuoso_support_ai Tool to use the Virtuoso AI support function Read podbc_describe_table Retrieve and return a dictionary containing the definition of a table, including column na Read podbc_get_schemas Retrieve and return a list of all schema names from the connected database.

All 14 Mcp Sqlalchemy 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 podbc_filter_table_names

What does the podbc_filter_table_names tool do? +

Retrieve and return a list containing information about tables whose names contain the substring. It is categorised as a Read tool in the Mcp Sqlalchemy MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on podbc_filter_table_names? +

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

What risk level is podbc_filter_table_names? +

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

Can I rate-limit podbc_filter_table_names? +

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

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

podbc_filter_table_names is provided by the Mcp Sqlalchemy MCP server (openlinksoftware/mcp-sqlalchemy-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 Sqlalchemy tool call.

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

CHECK YOUR STACK →