Low Risk

db_table_foreign_keys

Get foreign key relationships for a table

How to control db_table_foreign_keys ↓

AI agents call db_table_foreign_keys 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.

Low Risk

This tool retrieves and returns foreign key constraint information from database tables. It performs a read-only query of database schema metadata with no side effects, no data modifications, no code execution, and no destructive operations. The verb 'Get' confirms retrieval intent.

From the tool's definition Tool name 'db_table_foreign_keys' and description 'Get foreign key relationships for a table' indicate a retrieval operation that queries database metadata without modifying or executing any operations.

Documented attack patterns abuse exactly the kind of access db_table_foreign_keys 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_table_foreign_keys:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "db_table_foreign_keys": {}
  }
}

db_table_foreign_keys is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register DBJavaGenix — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the db_table_foreign_keys tool do? +

Get foreign key relationships for a table. It is categorised as a Read tool in the DBJavaGenix MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on db_table_foreign_keys? +

Register the DBJavaGenix MCP server in PolicyLayer and add a rule for db_table_foreign_keys: 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.

What risk level is db_table_foreign_keys? +

db_table_foreign_keys is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit db_table_foreign_keys? +

Yes. Add a rate_limit block to the db_table_foreign_keys 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.

How do I block db_table_foreign_keys completely? +

Set action: deny in the PolicyLayer policy for db_table_foreign_keys. 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.

What MCP server provides db_table_foreign_keys? +

db_table_foreign_keys 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.

Enforce policy on every DBJavaGenix tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.