New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

PostgreSQL_list_triggers

List all triggers on a specific table.

SERVERPostgres SOURCEmukul975/postgres-mcp-server
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mukul975-postgres-mcp-server/postgresql-list-triggers.md

What PostgreSQL_list_triggers does on Postgres

AI agents call PostgreSQL_list_triggers 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_list_triggers is rated Low

This tool queries and retrieves information about database triggers without modifying any data or executing arbitrary code. It is a straightforward read operation on database schema metadata, similar to SHOW or DESCRIBE commands. The blast radius of misuse is minimal—an attacker could learn about trigger definitions but cannot alter application logic or data through this tool alone.

From the tool's definition Tool name and description indicate retrieval of trigger metadata: 'List all triggers on a specific table.' No modification, execution, deletion, or financial operations are performed.

Questions about PostgreSQL_list_triggers

What does the PostgreSQL_list_triggers tool do? +

List all triggers on a specific table. It is categorised as a Read tool in the Postgres MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on PostgreSQL_list_triggers? +

Register the Postgres MCP server in PolicyLayer and add a rule for PostgreSQL_list_triggers: 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 Postgres. Nothing to install.

What risk level is PostgreSQL_list_triggers? +

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

Can I rate-limit PostgreSQL_list_triggers? +

Yes. Add a rate_limit block to the PostgreSQL_list_triggers 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 PostgreSQL_list_triggers completely? +

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

PostgreSQL_list_triggers is provided by the Postgres MCP server (mukul975/postgres-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Postgres, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Postgres's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.