List all webhook subscriptions on PostEverywhere for the current organization. Returns id, url, subscribed events, is_active, recent delivery stats. Note: the signing secret is NEVER included in list responses.
AI agents call list_webhooks to retrieve information from Posteverywhere without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
list_webhooks retrieves and queries webhook configuration metadata for the current organization. It has no side effects, does not create, modify, or delete data, and does not execute code or external operations. The security note about the signing secret not being included further confirms this is a read-only audit/status operation. Classification as Read is appropriate.
From the tool's definition Tool description explicitly states it 'List[s] all webhook subscriptions' and 'Returns id, url, subscribed events, is_active, recent delivery stats' — purely informational retrieval with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
List all webhook subscriptions on PostEverywhere for the current organization. Returns id, url, subscribed events, is_active, recent delivery stats. Note: the signing secret is NEVER included in list responses. It is categorised as a Read tool in the Posteverywhere MCP Server, which means it retrieves data without modifying state.
Register the Posteverywhere MCP server in PolicyLayer and add a rule for list_webhooks: 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 Posteverywhere. Nothing to install.
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 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_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 Posteverywhere MCP server (posteverywhere/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →