Retrieve all leads associated with a specific campaign, with optional filtering and pagination.
AI agents call smartlead_list_leads_by_campaign to retrieve information from SmartLead MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries lead data without creating, modifying, deleting, or executing external operations. It is a straightforward data retrieval function with optional filters, characteristic of a Read category tool. The blast radius of misuse is low—an AI could at worst access lead information it shouldn't see, but cannot modify, delete, or act upon it without other tools.
From the tool's definition Tool name contains 'list_leads' and description states 'Retrieve all leads associated with a specific campaign, with optional filtering and pagination.' The verb 'Retrieve' and the presence of filtering/pagination parameters indicate a read-only query…
Documented attack patterns abuse exactly the kind of access smartlead_list_leads_by_campaign gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SmartLead MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for smartlead_list_leads_by_campaign:
{
"version": "1",
"default": "deny",
"tools": {
"smartlead_list_leads_by_campaign": {}
}
}smartlead_list_leads_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.
Retrieve all leads associated with a specific campaign, with optional filtering and pagination. It is categorised as a Read tool in the SmartLead MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SmartLead MCP Server MCP server in PolicyLayer and add a rule for smartlead_list_leads_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 MCP Server. Nothing to install.
smartlead_list_leads_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_list_leads_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_list_leads_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_list_leads_by_campaign is provided by the SmartLead MCP Server MCP server (leadmagic/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 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.
116 SmartLead MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.