salesforce_query
Execute a SOQL query against Salesforce
This record as markdown: /tools/io-github-alifanov-scopegate/salesforce-query.md
What salesforce_query does on ScopeGate
AI agents invoke salesforce_query to trigger actions in ScopeGate. 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.
Why salesforce_query is rated High
The tool executes arbitrary SOQL queries against Salesforce. While SOQL is primarily a query language, executing arbitrary queries against a CRM containing sensitive customer data, financial records, and business intelligence represents high risk. The word 'Execute' in the description confirms active operation rather than passive retrieval.
From the tool's definition "Execute a SOQL query against Salesforce"
Attacks that exploit this kind of access
The rule that runs salesforce_query safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For salesforce_query, this is the rule to start with:
salesforce_query 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.
The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every salesforce_query call is checked against it from then on.
Questions about salesforce_query
Execute a SOQL query against Salesforce. It is categorised as a Execute tool in the ScopeGate MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ScopeGate MCP server in PolicyLayer and add a rule for salesforce_query: 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 ScopeGate. Nothing to install.
salesforce_query 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 salesforce_query 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 salesforce_query. 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.
salesforce_query is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
Across the catalogue