list_webhooks
AI agents call list_webhooks to retrieve information from Multilead Open API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the naming convention 'list_' clearly indicates this tool retrieves or enumerates webhook data. This is a Read operation with minimal risk—it accesses existing webhook metadata without creating, modifying, or deleting any data. The blast radius is low since an AI agent misusing this would only gain visibility into configured webhooks, not trigger dangerous actions or data modifications.
From the tool's definition Tool name is 'list_webhooks' which indicates a retrieval operation. The 'list' prefix is a standard Read operation pattern that queries and returns existing webhook configurations without modifying them.
Attacks that exploit this kind of access
list_webhooks. It is categorised as a Read tool in the Multilead Open API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Multilead Open API MCP Server 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 Multilead Open API MCP Server. 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 Multilead Open API MCP Server MCP server (vanman2024/multilead-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 →