list_workflow_triggers

List scheduled workflow triggers owned by the current user.

SERVERTodo for AI MCP Server SOURCEtodo-for-ai/todo-for-ai-mcp

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/todo-for-ai-todo-for-ai-mcp/list-workflow-triggers.md

WHAT IT DOES

What list_workflow_triggers does on Todo for AI MCP Server

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

RISK

Why list_workflow_triggers is rated Low

Even though list_workflow_triggers only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_workflow_triggers safely

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

list_workflow_triggers Allowed

list_workflow_triggers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Todo for AI MCP Server, apply this rule, and every list_workflow_triggers call is checked against it from then on.

FAQ

Questions about list_workflow_triggers

What does the list_workflow_triggers tool do? +

List scheduled workflow triggers owned by the current user. It is categorised as a Read tool in the Todo for AI MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_workflow_triggers? +

Register the Todo for AI MCP Server MCP server in PolicyLayer and add a rule for list_workflow_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 Todo for AI MCP Server. Nothing to install.

What risk level is list_workflow_triggers? +

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

Can I rate-limit list_workflow_triggers? +

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

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

list_workflow_triggers is provided by the Todo for AI MCP Server MCP server (todo-for-ai/todo-for-ai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Todo for AI MCP Server, and thousands of servers like it.

This server

All 244 Todo for AI MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →