List recent webhook delivery attempts for a specific webhook
AI agents call list_webhook_deliveries to retrieve information from Flux MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries historical webhook delivery data without creating, modifying, or deleting any information. It is a read-only operation that retrieves metadata about past webhook attempts. The blast radius is minimal—an agent listing webhook deliveries cannot cause direct harm to the system or data.
From the tool's definition Tool name 'list_webhook_deliveries' and description 'List recent webhook delivery attempts for a specific webhook' indicate a retrieval/query operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list_webhook_deliveries gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Flux MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_webhook_deliveries:
{
"version": "1",
"default": "deny",
"tools": {
"list_webhook_deliveries": {}
}
}list_webhook_deliveries is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List recent webhook delivery attempts for a specific webhook. It is categorised as a Read tool in the Flux MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Flux MCP Server MCP server in PolicyLayer and add a rule for list_webhook_deliveries: 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 Flux MCP Server. Nothing to install.
list_webhook_deliveries 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_webhook_deliveries 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_webhook_deliveries. 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_webhook_deliveries is provided by the Flux MCP Server MCP server (sirsjg/flux). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 25 Flux MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
25 Flux MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.