assign_leads_to_campaign
Assign one or more of the user's existing leads to one of the user's campaigns (both must be owned by the caller). Returns how many were assigned. Idempotent. Requires authentication.
This record as markdown: /tools/com-meta-council-decision-intelligence/assign-leads-to-campaign.md
What assign_leads_to_campaign does on Meta Council
AI agents use assign_leads_to_campaign to create or update resources in Meta Council, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meta Council environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
lead_ids | array | Yes | Lead ids to assign (from search_outreach_leads). |
campaign_id | string | Yes | Target campaign id (from list_outreach_campaigns). |
Parameters from the server's own tool schema.
Why assign_leads_to_campaign is rated Medium
This tool creates or modifies the relationship between leads and campaigns by assigning leads to a specific campaign. This is a reversible write operation (leads can be reassigned or unassigned). It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely retrieve data (Read).
From the tool's definition Tool description explicitly states it 'Assign[s] one or more of the user's existing leads to one of the user's campaigns', modifying the association between leads and campaigns. Marked as 'Idempotent', confirming reversible state change.
Attacks that exploit this kind of access
The rule that runs assign_leads_to_campaign safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Council, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For assign_leads_to_campaign, this is the rule to start with:
assign_leads_to_campaign stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every assign_leads_to_campaign call is checked against it from then on.
Questions about assign_leads_to_campaign
Assign one or more of the user's existing leads to one of the user's campaigns (both must be owned by the caller). Returns how many were assigned. Idempotent. Requires authentication. It is categorised as a Write tool in the Meta Council MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
assign_leads_to_campaign accepts 2 parameters: lead_ids, campaign_id. Required: lead_ids, campaign_id. The full parameter table on this page comes from the server's own tool schema.
Register the Meta Council MCP server in PolicyLayer and add a rule for assign_leads_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 Meta Council. Nothing to install.
assign_leads_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 assign_leads_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 assign_leads_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.
assign_leads_to_campaign is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Council, and thousands of servers like it.
This server
Across the catalogue