AI agents invoke test_webhook_subscription to trigger actions in Smokeball. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external HTTP request to a webhook endpoint, which is an active operation with external side effects. It doesn't read, write, or delete data — it executes an outbound call to a third-party system. Misuse could spam external endpoints or reveal webhook URLs, hence medium severity.
From the tool's definition Send a test notification to a webhook subscription endpoint
Attacks that exploit this kind of access
Send a test notification to a webhook subscription endpoint. It is categorised as a Execute tool in the Smokeball MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Smokeball MCP server in PolicyLayer and add a rule for test_webhook_subscription: 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.
test_webhook_subscription is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the test_webhook_subscription 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 test_webhook_subscription. 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.
test_webhook_subscription 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 →