List all schemas (databases/namespaces) available in the connected database
AI agents call db_list_schemas 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 retrieves database schema metadata (names of databases/namespaces). It has no side effects, does not modify data, does not execute code or commands, and does not delete anything. The blast radius of misuse is minimal—an agent can only learn what schemas exist, which is informational. This is a straightforward Read classification.
From the tool's definition Tool description states 'List all schemas' — a retrieval operation with no side effects. The verb 'list' is a classic Read operation that queries metadata without modifying or executing anything.
Attacks that exploit this kind of access
List all schemas (databases/namespaces) available in the connected database. 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_schemas: 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_schemas 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_schemas 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_schemas. 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_schemas 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 →