Test connectivity to a configured Sybase database
AI agents call test_database_connection to retrieve information from MCP Document Converter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Testing database connectivity is a read-only operation that verifies a connection without side effects. It does not create, modify, delete, or execute arbitrary operations on data. The tool only checks if the connection works, making it equivalent to a query/diagnostic operation with minimal blast radius if misused.
From the tool's definition Tool is named 'test_database_connection' and description states it 'Test connectivity to a configured Sybase database' — it performs a diagnostic check without modifying, executing queries against, or deleting data.
Attacks that exploit this kind of access
Test connectivity to a configured Sybase database. It is categorised as a Read tool in the MCP Document Converter MCP Server, which means it retrieves data without modifying state.
Register the MCP Document Converter MCP server in PolicyLayer and add a rule for test_database_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 MCP Document Converter. Nothing to install.
test_database_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_database_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_database_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_database_connection is provided by the MCP Document Converter MCP server (kittolau/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 →