Test whether the MCP server can connect to the configured ODBC database.
AI agents call ping_database 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.
The tool performs a read-only connectivity check. It queries the state of the database connection but produces no side effects, creates no data modifications, and executes no user-supplied logic. The blast radius of misuse is minimal—a false positive/negative connectivity status poses no security or operational risk. This is a benign diagnostic Read operation.
From the tool's definition Tool name 'ping_database' and description 'Test whether the MCP server can connect to the configured ODBC database' indicate a connection test that retrieves status information without modifying data or executing arbitrary queries.
Attacks that exploit this kind of access
Test whether the MCP server can connect to the configured ODBC database. 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 ping_database: 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.
ping_database 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 ping_database 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 ping_database. 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.
ping_database 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 →