PostgreSQL_get_trigger_performance_impact

What PostgreSQL_get_trigger_performance_impact does on Postgres

AI agents call PostgreSQL_get_trigger_performance_impact 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_trigger_performance_impact is rated Low

This tool retrieves and analyzes performance statistics about existing triggers. It reads diagnostic information from the database but does not execute triggers, modify data, delete anything, or incur financial costs. The 'analyze' verb here means introspection/reporting, not code execution. The low blast radius reflects that misuse would only expose performance data, not cause operational harm.

From the tool's definition Tool name contains 'get' and 'analyze', and description states 'Analyze trigger performance impact' — core Read operation querying performance metrics without modifying data or executing triggers.

The rule that runs PostgreSQL_get_trigger_performance_impact 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_trigger_performance_impact, this is the rule to start with:

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

Questions about PostgreSQL_get_trigger_performance_impact