List all tables in the Overlord SQLite database.
AI agents call db_list_tables to retrieve information from Overlord MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries database schema information (table names) without creating, modifying, deleting, or executing arbitrary commands. It is purely informational and has no side effects beyond reading metadata. The low severity reflects minimal blast radius—an agent can learn the database structure but cannot alter, delete, or access sensitive data through this tool alone.
From the tool's definition Tool name 'db_list_tables' and description 'List all tables in the Overlord SQLite database' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
List all tables in the Overlord SQLite database. It is categorised as a Read tool in the Overlord MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Overlord MCP Server 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 Overlord MCP Server. 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 Overlord MCP Server MCP server (skeeminator/overlord-mcp). 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 →