Execute SOQL query with auto-bulk switching for large result sets
AI agents invoke execute-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.
While SOQL is primarily a read operation (retrieving data), it is classified as Execute rather than Read because: (1) the tool executes dynamic queries whose behavior is determined by user-supplied arguments, (2) it is part of a Salesforce integration that includes destructive and code-execution capabilities, and (3) a malicious or erroneous SOQL query could cause significant side effects such as exfiltrating…
From the tool's definition Tool name 'execute-soql' and description 'Execute SOQL query' indicate dynamic query execution. SOQL (Salesforce Object Query Language) is a query language that can be used to read data, but critically, the sibling tool context (execute-apex, execute-sosl,…
Documented attack patterns abuse exactly the kind of access execute-soql gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Salesforce MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for execute-soql:
{
"version": "1",
"default": "deny",
"tools": {
"execute-soql": {
"limits": [
{
"counter": "execute-soql_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute-soql stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Execute SOQL query with auto-bulk switching for large result sets. 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 execute-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.
execute-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 execute-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 execute-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.
execute-soql is provided by the Salesforce MCP Server MCP server (jaworjar95/salesforce-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Salesforce MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Salesforce MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.