Fetch all the webhooks associated with a campaign using the campaign ID.
AI agents call smartlead_fetch_webhooks_by_campaign to retrieve information from Smartlead Simplified MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Fetching webhook configurations associated with a campaign is a read-only operation that retrieves existing data without modifying, executing, or deleting anything. It does not move money, execute code, or cause any irreversible changes. The blast radius of misuse is low - an agent could enumerate webhooks but cannot alter campaign infrastructure, trigger payments, or destroy data.
From the tool's definition The tool is called 'fetch_webhooks_by_campaign' and the description states it 'Fetch all the webhooks associated with a campaign' - these are explicit indicators of a retrieval/query operation with no side effects.
Documented attack patterns abuse exactly the kind of access smartlead_fetch_webhooks_by_campaign gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Smartlead Simplified MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for smartlead_fetch_webhooks_by_campaign:
{
"version": "1",
"default": "deny",
"tools": {
"smartlead_fetch_webhooks_by_campaign": {}
}
}smartlead_fetch_webhooks_by_campaign is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch all the webhooks associated with a campaign using the campaign ID. It is categorised as a Read tool in the Smartlead Simplified MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Smartlead Simplified MCP Server MCP server in PolicyLayer and add a rule for smartlead_fetch_webhooks_by_campaign: 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 Smartlead Simplified MCP Server. Nothing to install.
smartlead_fetch_webhooks_by_campaign 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 smartlead_fetch_webhooks_by_campaign 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 smartlead_fetch_webhooks_by_campaign. 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.
smartlead_fetch_webhooks_by_campaign is provided by the Smartlead Simplified MCP Server MCP server (jonathan-politzki/smartlead-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Smartlead Simplified MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
78 Smartlead Simplified MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.