List available database schemas/catalogs from the configured ODBC connection.
AI agents call list_schemas to retrieve information from OpenLink MCP Server for ODBC without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about database schemas without executing queries, modifying data, or triggering external operations. It is purely informational and read-only, with negligible blast radius if misused by an agent. The confidence is high because the purpose is unambiguous.
From the tool's definition Tool name is 'list_schemas' and description states it 'List[s] available database schemas/catalogs' — a querying operation with no modification or deletion of data.
Attacks that exploit this kind of access
List available database schemas/catalogs from the configured ODBC connection. It is categorised as a Read tool in the OpenLink MCP Server for ODBC MCP Server, which means it retrieves data without modifying state.
Register the OpenLink MCP Server for ODBC 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 OpenLink MCP Server for ODBC. 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 OpenLink MCP Server for ODBC MCP server (pvsmark/pvs-odbc-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 →