List all configured webhooks.
AI agents call keyid_list_webhooks to retrieve information from KeyID Agent Kit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves webhook configurations without modifying, executing, or deleting anything. However, severity is elevated to 'medium' rather than 'low' because webhook configurations may contain sensitive information such as target URLs, authentication tokens, or event triggers that could expose system architecture or be used to plan further attacks if an AI agent gains unauthorized access to this list.
From the tool's definition Tool name 'keyid_list_webhooks' and description 'List all configured webhooks' indicate a query/retrieval operation with no side effects. The verb 'list' is characteristic of Read operations.
Attacks that exploit this kind of access
List all configured webhooks. It is categorised as a Read tool in the KeyID Agent Kit MCP Server, which means it retrieves data without modifying state.
Register the KeyID Agent Kit MCP server in PolicyLayer and add a rule for keyid_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 KeyID Agent Kit. Nothing to install.
keyid_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 keyid_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 keyid_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.
keyid_list_webhooks is provided by the KeyID Agent Kit MCP server (keyid-ai/agent-kit). 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 →