List all registered webhooks for your account.
AI agents call list_webhooks to retrieve information from Postcardbot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays data about registered webhooks with no side effects. It is a straightforward query operation analogous to a list or get operation. While webhook configurations may contain sensitive information (URLs, API keys), the tool itself performs no destructive, executable, or financial action.
From the tool's definition Tool name 'list_webhooks' and description 'List all registered webhooks for your account' indicate a read-only query operation that retrieves existing webhook configurations without modifying or executing any actions.
Attacks that exploit this kind of access
List all registered webhooks for your account. It is categorised as a Read tool in the Postcardbot MCP Server, which means it retrieves data without modifying state.
Register the Postcardbot 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 Postcardbot. 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 Postcardbot MCP server (postcardbot/mcp-server). 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 →