AI agents call list_dsns to retrieve information from Mcp Odbc without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about available ODBC data sources without creating, modifying, deleting, or executing any operations. It is a pure information-gathering action with no side effects, fitting the 'Read' category. Severity is low because listing DSNs does not expose sensitive data directly and has minimal blast radius—it merely enumerates connection options.
From the tool's definition Tool name 'list_dsns' and description 'List all ODBC data sources (DSNs) configured on this system' indicate querying/enumerating system configuration without modification.
Attacks that exploit this kind of access
List all ODBC data sources (DSNs) configured on this system. It is categorised as a Read tool in the Mcp Odbc MCP Server, which means it retrieves data without modifying state.
Register the Mcp Odbc MCP server in PolicyLayer and add a rule for list_dsns: 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 Odbc. Nothing to install.
list_dsns 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_dsns 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_dsns. 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_dsns is provided by the Mcp Odbc MCP server (phil-cheesman/mcp-odbc). 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 →