Resume the execution of campaign steps for a specific lead
AI agents invoke resume_lead_execution to trigger actions in Multilead Open API MCP Server. 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 resumes an ongoing process (campaign step execution) for a lead, which constitutes triggering external operations. It's not purely writing data but actively executing campaign logic/actions that may send emails or perform outreach. Severity is medium as it affects a single lead's campaign flow.
From the tool's definition 'Resume the execution of campaign steps for a specific lead' — triggers execution of campaign steps
Attacks that exploit this kind of access
Resume the execution of campaign steps for a specific lead. It is categorised as a Execute tool in the Multilead Open API MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Multilead Open API MCP Server MCP server in PolicyLayer and add a rule for resume_lead_execution: 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 Multilead Open API MCP Server. Nothing to install.
resume_lead_execution 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 resume_lead_execution 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 resume_lead_execution. 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.
resume_lead_execution is provided by the Multilead Open API MCP Server MCP server (vanman2024/multilead-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 →