List all tables and views with row counts, types, and schema information
AI agents call db_list_tables to retrieve information from RunContext without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns structural metadata about database objects (tables, views, counts, types, schema info) without side effects. It is purely informational and fits the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch)'. The low severity reflects minimal blast radius—metadata exposure is a concern but cannot cause data loss or unauthorized modifications.
From the tool's definition Tool name 'db_list_tables' and description 'List all tables and views with row counts, types, and schema information' indicate retrieval of metadata only. No modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
List all tables and views with row counts, types, and schema information. It is categorised as a Read tool in the RunContext MCP Server, which means it retrieves data without modifying state.
Register the RunContext MCP server in PolicyLayer and add a rule for db_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 RunContext. Nothing to install.
db_list_tables is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the db_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.
Set action: deny in the PolicyLayer policy for db_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.
db_list_tables is provided by the RunContext MCP server (quiet-victory-labs/runcontext). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →