run_lead_operation
AI agents invoke run_lead_operation to trigger actions in Salesforce MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool operates on Salesforce Lead records within a CRM system. While the tool description is empty, the server description explicitly states it supports CRUD operations (Create, Read, Update, Delete) on Lead records. CRUD operations that include modification and deletion capabilities classify as Execute (or potentially Destructive if delete is prominent).
From the tool's definition Tool name 'run_lead_operation' with empty description, but server description indicates it performs 'CRUD operations on records such as Leads' and executes operations on Salesforce data alongside SOQL query tools (run_soql, run_account_operation,…
Attacks that exploit this kind of access
run_lead_operation. It is categorised as a Execute tool in the Salesforce MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Salesforce MCP Server MCP server in PolicyLayer and add a rule for run_lead_operation: 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 Salesforce MCP Server. Nothing to install.
run_lead_operation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_lead_operation 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 run_lead_operation. 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.
run_lead_operation is provided by the Salesforce MCP Server MCP server (tweiss777/salesforce-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 →