List all schemas (libraries) in the IBM DB2i database. Optionally filter by name pattern using * as wildcard.
AI agents call list_schemas to retrieve information from Db2i without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a metadata inspection operation that queries and returns schema information with no side effects. It performs no write, delete, execute, or financial operations. The read-only nature is explicitly confirmed by the server's design philosophy. Severity is low due to minimal blast radius—it only exposes schema names, which are typically non-sensitive structural information in most organizations.
From the tool's definition Tool lists database schemas/libraries without modification. Description states "List all schemas" with optional filtering. Server description emphasizes "read-only SQL commands and schema inspection tools" with "secure access to table metadata."
Documented attack patterns abuse exactly the kind of access list_schemas gives an agent:
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_schemas:
{
"version": "1",
"default": "deny",
"tools": {
"list_schemas": {}
}
}list_schemas is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all schemas (libraries) in the IBM DB2i database. Optionally filter by name pattern using * as wildcard. It is categorised as a Read tool in the Db2i MCP Server, which means it retrieves data without modifying state.
Register the Db2i MCP server in PolicyLayer and add a rule for 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 Db2i. Nothing to install.
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 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 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.
list_schemas 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.
Start from Db2i, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Db2i tools catalogued and risk-classified — across an index of 43,000+ MCP servers.