Detect FK cycles in schema (anti-pattern). Returns cycles list and
AI agents call schema_check_cycles 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 schema introspection—analyzing foreign key relationships to identify cycles. It retrieves and reports information about the database structure but does not create, modify, delete, or execute code. The output is a read-only analysis result. No side effects or external operations are triggered. This is a classic Read operation.
From the tool's definition Tool name 'schema_check_cycles' and description 'Detect FK cycles in schema (anti-pattern). Returns cycles list' indicate a query/analysis operation that retrieves and reports on schema structure without modifying data or executing external operations.
Documented attack patterns abuse exactly the kind of access schema_check_cycles 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_check_cycles:
{
"version": "1",
"default": "deny",
"tools": {
"schema_check_cycles": {}
}
}schema_check_cycles 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.
Detect FK cycles in schema (anti-pattern). Returns cycles list and. 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_check_cycles: 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_check_cycles 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_check_cycles 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_check_cycles. 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_check_cycles 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.