Get all constraints (primary keys, foreign keys, unique constraints) for a specific table. ${sessionConfig ?
AI agents call get_table_constraints to retrieve information from Db2i without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs metadata introspection only—it queries and returns constraint information without altering, creating, or deleting any data or schema objects. It has no side effects and poses minimal risk even if invoked repeatedly or with unexpected arguments, as it only retrieves existing schema information.
From the tool's definition Tool retrieves constraint metadata for a table (primary keys, foreign keys, unique constraints) via schema inspection. Description indicates read-only retrieval of table metadata with no modification or deletion capability.
Documented attack patterns abuse exactly the kind of access get_table_constraints gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Db2i, and nothing reaches the server without passing your rules. This is the rule we recommend for get_table_constraints:
{
"version": "1",
"default": "deny",
"tools": {
"get_table_constraints": {}
}
}get_table_constraints 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.
Get all constraints (primary keys, foreign keys, unique constraints) for a specific table. ${sessionConfig ?. It is categorised as a Read tool in the Db2i MCP Server, which means it retrieves data without modifying state.
Register the Db2i MCP server in PolicyLayer and add a rule for get_table_constraints: 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 Db2i. Nothing to install.
get_table_constraints 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 get_table_constraints 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 get_table_constraints. 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.
get_table_constraints is provided by the Db2i MCP server (strom-capital/mcp-server-db2i). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Db2i, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Db2i tools catalogued and risk-classified — across an index of 43,000+ MCP servers.