run_soql
AI agents invoke run_soql 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.
SOQL query execution is fundamentally an Execute action—it triggers external operations (Salesforce queries) whose side effects depend entirely on the query arguments provided by the AI agent. While SOQL is primarily a read mechanism, the tool's placement in a CRUD-capable server and empty description create ambiguity about whether it permits INSERT/UPDATE/DELETE operations.
From the tool's definition Tool name 'run_soql' indicates execution of SOQL (Salesforce Object Query Language) queries. Server description states it 'executing SOQL queries and performing CRUD operations on records.' SOQL queries can retrieve data, but given the context of sibling…
Attacks that exploit this kind of access
run_soql. 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_soql: 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_soql 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_soql 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_soql. 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_soql 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 →