pipeline_webhook_route_list
List routing branches (payload filter -> destination column) in evaluation order, for one webhook_id or the whole workspace. Returns {data: Route[]}.
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/pipeline-webhook-route-list.md
What pipeline_webhook_route_list does on Max MCP Server
AI agents call pipeline_webhook_route_list to retrieve information from Max MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why pipeline_webhook_route_list is rated Low
Tool retrieves webhook routing configuration without creating, modifying, or deleting data.
From the tool's definition List routing branches, returns data, no modification or deletion
Attacks that exploit this kind of access
The rule that runs pipeline_webhook_route_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Max MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pipeline_webhook_route_list, this is the rule to start with:
pipeline_webhook_route_list 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 Max MCP Server, apply this rule, and every pipeline_webhook_route_list call is checked against it from then on.
Questions about pipeline_webhook_route_list
List routing branches (payload filter -> destination column) in evaluation order, for one webhook_id or the whole workspace. Returns {data: Route[]}. It is categorised as a Read tool in the Max MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for pipeline_webhook_route_list: 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 Max MCP Server. Nothing to install.
pipeline_webhook_route_list 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 pipeline_webhook_route_list 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 pipeline_webhook_route_list. 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.
pipeline_webhook_route_list is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Max MCP Server, and thousands of servers like it.
This server
Across the catalogue