update_lead
AI agents use update_lead 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 modifies existing lead records, which is reversible (changes can be undone or overwritten), placing it in the Write category. Severity is medium because misuse could alter lead data affecting business processes, but the impact is limited to individual lead records and is not destructive or financial in nature.
From the tool's definition Tool name 'update_lead' indicates modification of lead data within the Multilead platform. The sibling tools 'add_leads_to_campaign', 'assign_tag_to_lead', and 'add_keywords_to_blacklist' confirm this server manages lead and campaign data that can be modified.
Attacks that exploit this kind of access
update_lead. 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 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 Multilead Open API MCP Server. 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 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 →