convert_lead_to_deal
Convert an owned outreach lead into a deal and advance the lead into the deal stage of the funnel (never downgrading an already-closed lead). Optional deal fields mirror create_deal; lead_id is required.
This record as markdown: /tools/com-meta-council-decision-intelligence/convert-lead-to-deal.md
What convert_lead_to_deal does on Meta Council
AI agents use convert_lead_to_deal 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 |
|---|---|---|---|
notes | string | — | |
stage | string | — | |
title | string | — | |
amount | number | — | |
company | string | — | |
lead_id | string | Yes | |
currency | string | — | Exactly three ASCII letters, such as USD; saved uppercase. Omit for USD. Syntax only, not an ISO registry. |
probability | integer | — | |
expected_close_date | string | — | ISO date YYYY-MM-DD. |
Parameters from the server's own tool schema.
Why convert_lead_to_deal is rated Medium
An AI agent can call convert_lead_to_deal faster than any human can review: one bad instruction and it creates or modifies resources in Meta Council by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs convert_lead_to_deal 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 convert_lead_to_deal, this is the rule to start with:
convert_lead_to_deal 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 convert_lead_to_deal call is checked against it from then on.
Questions about convert_lead_to_deal
Convert an owned outreach lead into a deal and advance the lead into the deal stage of the funnel (never downgrading an already-closed lead). Optional deal fields mirror create_deal; lead_id is required. 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.
convert_lead_to_deal accepts 9 parameters: notes, stage, title, amount, company, lead_id, currency, probability, expected_close_date. Required: lead_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 convert_lead_to_deal: 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.
convert_lead_to_deal 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 convert_lead_to_deal 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 convert_lead_to_deal. 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.
convert_lead_to_deal 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