update_lead
Edit an existing lead in the Leads CRM (crm_leads): name, email, phone, location, do-not-contact flag/reason, lifecycle state (new/active/flagged/archived), or the synopsis fields (title, company_name, tags, notes). Identify the lead with lead_id or email_lookup. Moving state to 'flagged' or 'arc...
This record as markdown: /tools/com-getfreedomos-freedom-mcp/update-lead.md
What update_lead does on Freedom Mcp
AI agents use update_lead to create or update resources in Freedom Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freedom Mcp environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | New full name. |
tags | array | — | Replacement tag list — folded into synopsis_jsonb.manual_entry. |
email | string | — | New email (normalized to lowercase/trim). Rejected if it already belongs to another lead in this company. |
notes | string | — | Notes about the lead — folded into synopsis_jsonb.manual_entry. |
phone | string | — | New phone number. |
state | string | — | New lifecycle state. state_reason is REQUIRED when moving to 'flagged' or 'archived'. |
title | string | — | Job title — folded into synopsis_jsonb.manual_entry (other manual_entry keys are preserved). |
lead_id | string | — | UUID of the lead to update. Provide this OR email_lookup. |
location | string | — | New location. |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
company_name | string | — | Company they work for — folded into synopsis_jsonb.manual_entry. |
email_lookup | string | — | The lead's CURRENT email, used to find it. Provide this OR lead_id. |
Parameters from the server's own tool schema.
Why update_lead is rated Medium
This tool modifies customer/lead data in a reversible manner (state can be moved off archived; fields can be re-edited). It does not execute code, delete permanently, or move money. The medium severity reflects potential misuse risk: an agent could spam or alter leads, corrupt customer records, or inappropriately flag/archive prospects, impacting business operations and customer relationships.
From the tool's definition "Edit an existing lead in the Leads CRM" — creates or modifies CRM data reversibly. Tool permits updates to name, email, phone, location, lifecycle state, and notes.
Risk signalsHigh parameter count (15 properties)
Attacks that exploit this kind of access
The rule that runs update_lead safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freedom Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_lead, this is the rule to start with:
update_lead 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 Freedom Mcp, apply this rule, and every update_lead call is checked against it from then on.
Questions about update_lead
Edit an existing lead in the Leads CRM (crm_leads): name, email, phone, location, do-not-contact flag/reason, lifecycle state (new/active/flagged/archived), or the synopsis fields (title, company_name, tags, notes). Identify the lead with lead_id or email_lookup. Moving state to 'flagged' or 'archived' REQUIRES state_reason. Archiving sets archived_at (safe-archive, reversible — move state off archived to restore it). If the lead's outreach is set to auto and you move it off 'active', outreach is demoted back to manual (auto-outreach is only valid while active). Use when the operator or an agent needs to fix or maintain lead data — wrong email, bad name, DNC request, or a lifecycle move — instead of telling the user to edit it in the UI. Routing: CRM/sales → edit a lead's fields, status, or DNC flag → use this (NOT update_lead_status/log_activity — those are removed) [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.]. It is categorised as a Write tool in the Freedom Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_lead accepts 12 parameters: name, tags, email, notes, phone, state, title, lead_id, location, companyId, company_name, email_lookup. Required: companyId. The full parameter table on this page comes from the server's own tool schema.
Register the Freedom MCP server in PolicyLayer and add a rule for update_lead: 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 Freedom Mcp. Nothing to install.
update_lead 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 update_lead 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 update_lead. 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.
update_lead is provided by the Freedom MCP server (https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freedom, and thousands of servers like it.
This server
Across the catalogue