Executes a SOSL search against Salesforce
AI agents invoke run_sosl_search 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 search execution qualifies as Execute rather than Read because it involves triggering a search operation against a live system whose scope and results depend on the search string provided by the caller. While not as severe as Destructive (which would require deletion) or Financial operations, misuse could expose sensitive Salesforce data at scale.
From the tool's definition Tool executes a SOSL search ('Executes a SOSL search against Salesforce'), which is a query execution that can retrieve sensitive data from Salesforce objects.
Attacks that exploit this kind of access
Executes a SOSL search against Salesforce. 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_sosl_search: 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_sosl_search 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_sosl_search 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_sosl_search. 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_sosl_search is provided by the Salesforce MCP Server MCP server (steffensbola/salesforce-mcp-ts). 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 →