Execute SOSL search with multi-object support
AI agents invoke execute-sosl 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.
SOSL execution is a code execution primitive in Salesforce. While primarily a read operation, SOSL queries are dynamically constructed and can be manipulated through prompt injection to access unintended data or objects. The tool executes a search command whose effects depend entirely on the query arguments provided by the AI agent.
From the tool's definition execute-sosl performs 'Execute SOSL search' — SOSL (Salesforce Object Search Language) is a query language that searches across multiple Salesforce objects and can potentially be exploited with injection attacks or to exfiltrate sensitive data at scale.
Documented attack patterns abuse exactly the kind of access execute-sosl 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-sosl:
{
"version": "1",
"default": "deny",
"tools": {
"execute-sosl": {
"limits": [
{
"counter": "execute-sosl_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute-sosl 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 SOSL search with multi-object support. 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-sosl: 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-sosl 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-sosl 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-sosl. 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-sosl 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.