This record as markdown: /tools/io-github-devopam-mcpg/list-triggers.md
What list_triggers does on Mcpg
AI agents call list_triggers to retrieve information from Mcpg without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_triggers is rated Low
This tool retrieves or enumerates trigger definitions from PostgreSQL, which is a non-destructive query operation. No side effects are mentioned or implied by the name. Although the description is empty, the naming convention clearly indicates a retrieval operation.
From the tool's definition Tool name 'list_triggers' indicates a query operation that retrieves trigger metadata from the PostgreSQL database. The 'list' prefix is characteristic of Read operations that enumerate database objects without modification.
Attacks that exploit this kind of access
The rule that runs list_triggers safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_triggers, this is the rule to start with:
list_triggers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcpg, apply this rule, and every list_triggers call is checked against it from then on.
Questions about list_triggers
list_triggers is a read tool on the Mcpg MCP server. It is categorised as a Read tool in the Mcpg MCP Server, which means it retrieves data without modifying state.
Register the Mcpg MCP server in PolicyLayer and add a rule for 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 Mcpg. Nothing to install.
list_triggers 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 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.
Set action: deny in the PolicyLayer policy for 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.
list_triggers is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcpg, and thousands of servers like it.
This server
Across the catalogue