PostgreSQL_get_all_constraints

What PostgreSQL_get_all_constraints does on Postgres

AI agents call PostgreSQL_get_all_constraints to retrieve information from Postgres without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why PostgreSQL_get_all_constraints is rated Low

This tool queries and returns constraint information from a PostgreSQL database without modifying, deleting, or executing any operations. It is a read-only introspection operation that retrieves schema metadata. The blast radius of misuse is minimal—an agent could gather schema information but cannot alter database structure or data.

From the tool's definition Tool name and description indicate retrieval of constraint metadata: 'Get all table constraints' with no mention of modification, deletion, or execution capabilities. Returns data about CHECK, UNIQUE, PRIMARY KEY, and FOREIGN KEY constraints.

The rule that runs PostgreSQL_get_all_constraints safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Postgres, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For PostgreSQL_get_all_constraints, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "PostgreSQL_get_all_constraints": {}
  }
}

Questions about PostgreSQL_get_all_constraints