return_lead_to_campaign
AI agents use return_lead_to_campaign to create or update resources in Multilead Open API MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Multilead Open API MCP Server environment.
The tool appears to update lead-campaign relationships, which is a reversible write operation modifying data state rather than executing arbitrary code or causing destructive changes. The empty description lowers confidence slightly, but the naming convention and sibling tools strongly suggest a write classification.
From the tool's definition Tool name 'return_lead_to_campaign' indicates a modification operation that moves or returns a lead to a campaign, which is a reversible write action.
Attacks that exploit this kind of access
return_lead_to_campaign. It is categorised as a Write tool in the Multilead Open API MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Multilead Open API MCP Server MCP server in PolicyLayer and add a rule for return_lead_to_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 Multilead Open API MCP Server. Nothing to install.
return_lead_to_campaign is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the return_lead_to_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 return_lead_to_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.
return_lead_to_campaign 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 →