Group tables into business clusters via Union-Find on FK connectivity.
AI agents call schema_cluster_tables 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.
schema_cluster_tables is a read-only analysis tool that examines database schema structure (foreign key relationships) and produces organizational insights. It groups related tables for visualization and code generation planning purposes but does not retrieve sensitive data, does not modify any tables, does not execute queries, and does not perform destructive operations.
From the tool's definition Tool groups tables into clusters based on foreign key connectivity using Union-Find algorithm. It performs analysis and clustering of existing schema metadata without modifying, deleting, or executing external operations.
Documented attack patterns abuse exactly the kind of access schema_cluster_tables 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 schema_cluster_tables:
{
"version": "1",
"default": "deny",
"tools": {
"schema_cluster_tables": {}
}
}schema_cluster_tables 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.
Group tables into business clusters via Union-Find on FK connectivity. 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 schema_cluster_tables: 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.
schema_cluster_tables 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 schema_cluster_tables 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 schema_cluster_tables. 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.
schema_cluster_tables 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.