Retrieve and return a list of all schema names from the connected database.
AI agents call podbc_get_schemas to retrieve information from MCP PyODBC Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves schema names from a database connection—a pure query operation with no capability to modify, delete, or execute arbitrary code. It is informational metadata access only. The blast radius of misuse is minimal (information disclosure about database structure), making it low severity.
From the tool's definition Tool name 'podbc_get_schemas' and description 'Retrieve and return a list of all schema names from the connected database' indicate a read-only operation that queries metadata without modification or side effects.
Attacks that exploit this kind of access
Retrieve and return a list of all schema names from the connected database. It is categorised as a Read tool in the MCP PyODBC Server MCP Server, which means it retrieves data without modifying state.
Register the MCP PyODBC Server MCP server in PolicyLayer and add a rule for podbc_get_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 MCP PyODBC Server. Nothing to install.
podbc_get_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 podbc_get_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 podbc_get_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.
podbc_get_schemas is provided by the MCP PyODBC Server MCP server (openlinksoftware/mcp-pyodbc-server). 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 →