Query records from any Salesforce object using SOQL, including relationship queries. Examples: 1. Parent-to-child query (e.g., Account with Contacts): - objectName:
AI agents invoke salesforce_query_records 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.
This tool executes SOQL queries against Salesforce, which is an Execute-category action. While typical SOQL is read-only, the tool allows arbitrary query execution including relationship queries across any object. The server description also mentions 'modifying and managing objects and records,' and sibling tools like salesforce_dml_records suggest this environment handles sensitive CRM data.
From the tool's definition "Query records from any Salesforce object using SOQL" — executes arbitrary SOQL queries against Salesforce data
Documented attack patterns abuse exactly the kind of access salesforce_query_records 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 salesforce_query_records:
{
"version": "1",
"default": "deny",
"tools": {
"salesforce_query_records": {
"limits": [
{
"counter": "salesforce_query_records_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}salesforce_query_records 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.
Query records from any Salesforce object using SOQL, including relationship queries. Examples: 1. Parent-to-child query (e.g., Account with Contacts): - objectName:. 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 salesforce_query_records: 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.
salesforce_query_records 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_records 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_records. 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_records is provided by the Salesforce MCP Server MCP server (surajadsul/mcp-server-salesforce). 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.
6 Salesforce MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.