AI agents call test_connection to retrieve information from Omnibase without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a test/validation operation on an existing connection and returns diagnostic information (status, latency, error messages). This is a non-destructive information retrieval operation with no side effects on data. While it may reveal error details, it does not read, modify, delete, or execute arbitrary code—it only checks connectivity.
From the tool's definition Tool name 'test_connection' and description 'Test a specific database connection. Returns status, latency, and the actual driver error on failure.' indicates a diagnostic/query operation that retrieves connection status information without modifying data or…
Attacks that exploit this kind of access
Test a specific database connection. Returns status, latency, and the actual driver error on failure. Use this to diagnose connection issues. It is categorised as a Read tool in the Omnibase MCP Server, which means it retrieves data without modifying state.
Register the Omnibase MCP server in PolicyLayer and add a rule for test_connection: 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 Omnibase. Nothing to install.
test_connection 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 test_connection 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 test_connection. 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.
test_connection is provided by the Omnibase MCP server (omnibase-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 →