list_webhooks
AI agents call list_webhooks to retrieve information from Thesma MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list_' prefix strongly suggests a query/enumeration operation with no side effects. While the description is empty (reducing confidence slightly from 0.95 to 0.9), the naming convention and the context of a data access server indicate this retrieves webhook configurations rather than creating, modifying, or deleting them. No data is modified, deleted, or financial obligations created.
From the tool's definition Tool name 'list_webhooks' indicates a retrieval operation that lists existing webhook configurations. The server context provides access to public data sources (SEC filings, BLS employment, Census demographics, SBA lending data) via queries, and webhook…
Attacks that exploit this kind of access
list_webhooks. It is categorised as a Read tool in the Thesma MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Thesma 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 Thesma 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 Thesma MCP Server MCP server (thesma-dev/thesma-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 →