Remove a specific tag from a specific lead
AI agents use remove_tag_from_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.
Removing a tag from a lead modifies the lead's metadata but does not delete the lead itself or the tag globally. This is a reversible modification (the tag can be re-assigned), making it a Write operation. The blast radius is low since it only affects a single tag on a single lead.
From the tool's definition 'Remove a specific tag from a specific lead' — removes a tag association from a lead record
Attacks that exploit this kind of access
Remove a specific tag from a specific 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 remove_tag_from_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.
remove_tag_from_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 remove_tag_from_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 remove_tag_from_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.
remove_tag_from_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 →