run_account_operation
AI agents invoke run_account_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.
This tool executes operations on Salesforce Account records. While the name alone is ambiguous, the server context confirms it performs CRUD operations—meaning it can Create, Read, Update, or Delete Account data. This spans Write (create/update) and potentially Destructive (delete) actions.
From the tool's definition Tool name 'run_account_operation' combined with server description stating it 'performs CRUD operations on records' and 'enables AI assistants to interact with Salesforce CRM.' The sibling tools include 'run_lead_operation' and 'run_opportunity_operation'…
Attacks that exploit this kind of access
run_account_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_account_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_account_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_account_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_account_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_account_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 →