List all active webhook subscriptions for the authenticated user. Returns webhook ID, URL, subscribed events, and creation date. Requires authentication.
Handles credentials or secrets (apiKey)
Part of the Timergy MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call list_webhooks to retrieve information from Timergy without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though list_webhooks only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
list_webhooks:
rules:
- action: allowSee the full Timergy policy for all 22 tools.
List all active webhook subscriptions for the authenticated user. Returns webhook ID, URL, subscribed events, and creation date. Requires authentication.. It is categorised as a Read tool in the Timergy MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for list_webhooks. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Timergy MCP server.
list_webhooks 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_webhooks rule in your Intercept 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 Intercept policy for list_webhooks. 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_webhooks is provided by the Timergy MCP server (@timergy/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept