list_workflows

List registered workflows with optional filtering by tags or labels.

SERVERFrontmcp SOURCEagentfront/frontmcp

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/frontmcp/list-workflows.md

WHAT IT DOES

What list_workflows does on Frontmcp

AI agents call list_workflows to retrieve information from Frontmcp 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_workflows is rated Low

This tool retrieves and lists workflow metadata with optional filters. It has no side effects, does not execute code, and does not modify state. It is a standard information-retrieval operation. The sibling tools (admin_action, admin-background-job, admin-only) suggest this server manages sensitive operations, but list_workflows itself is strictly read-only.

From the tool's definition Tool name is 'list_workflows' and description states it 'List registered workflows' — a pure read/query operation with optional filtering parameters. No modification, deletion, or execution of workflows is performed.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_workflows safely

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

list_workflows Allowed

list_workflows 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_workflows": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every list_workflows call is checked against it from then on.

FAQ

Questions about list_workflows

What does the list_workflows tool do? +

List registered workflows with optional filtering by tags or labels. It is categorised as a Read tool in the Frontmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_workflows? +

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

What risk level is list_workflows? +

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

Can I rate-limit list_workflows? +

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

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

list_workflows is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Front, and thousands of servers like it.

This server

All 206 Front tools →

Across the catalogue

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

Guides

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