AI agents call list_webhook_subscriptions to retrieve information from Smokeball without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation. It retrieves webhook subscription metadata and configuration but does not create, modify, delete, or trigger any external operations. The blast radius of misuse is minimal—an attacker gains visibility into webhook configurations but cannot alter them or cause irreversible damage. This is categorized as Read.
From the tool's definition list_webhook_subscriptions lists active webhook subscriptions without modifying, deleting, or executing any actions. The verb 'list' and the descriptive nature ('List all active webhook subscriptions') indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all active webhook subscriptions. It is categorised as a Read tool in the Smokeball MCP Server, which means it retrieves data without modifying state.
Register the Smokeball MCP server in PolicyLayer and add a rule for list_webhook_subscriptions: 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 Smokeball. Nothing to install.
list_webhook_subscriptions 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_webhook_subscriptions 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_webhook_subscriptions. 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_webhook_subscriptions is provided by the Smokeball MCP server (rosenadvertising/smokeball-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 →