AI agents call db_query_table_exists to retrieve information from DBJavaGenix without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple existence check on a database table—a metadata query with no side effects. It retrieves schema information only and cannot modify, delete, or execute code. The blast radius of misuse is minimal (information disclosure about table existence), making this a low-severity Read operation.
From the tool's definition Tool name 'db_query_table_exists' and description 'Check if a table exists in the database' indicate a read-only metadata query with no data retrieval or modification.
Documented attack patterns abuse exactly the kind of access db_query_table_exists gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DBJavaGenix, and nothing reaches the server without passing your rules. This is the rule we recommend for db_query_table_exists:
{
"version": "1",
"default": "deny",
"tools": {
"db_query_table_exists": {}
}
}db_query_table_exists is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check if a table exists in the database. It is categorised as a Read tool in the DBJavaGenix MCP Server, which means it retrieves data without modifying state.
Register the DBJavaGenix MCP server in PolicyLayer and add a rule for db_query_table_exists: 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 DBJavaGenix. Nothing to install.
db_query_table_exists 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 db_query_table_exists 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 db_query_table_exists. 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.
db_query_table_exists is provided by the DBJavaGenix MCP server (zhaoxingpeng/dbjavagenix). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 33 DBJavaGenix tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
33 DBJavaGenix tools catalogued and risk-classified — across an index of 42,500+ MCP servers.