Query records from any Salesforce object using SOQL, including relationship queries. NOTE: For queries with GROUP BY, aggregate functions (COUNT, SUM, AVG, etc.), or HAVING clauses, use salesforce_aggregate_query instead. Examples: 1. Parent-to-child query (e.g., Account with Contacts): - objectN...
AI agents call salesforce_query_records to retrieve information from Salesforce MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries Salesforce data using SOQL—a read-only operation with no side effects on data state. However, severity is medium (not low) because: (1) queries can access sensitive customer/business data across multiple related objects via relationship queries, (2) an AI agent could be manipulated to extract confidential information, and (3) the 'any Salesforce object' scope is broad.
From the tool's definition Tool description states it "Query records from any Salesforce object using SOQL" with explicit examples of relationship queries. The name 'salesforce_query_records' and verb 'Query' indicate data retrieval without modification.
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": {}
}
}salesforce_query_records is read-only, so it stays allowed — but 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. NOTE: For queries with GROUP BY, aggregate functions (COUNT, SUM, AVG, etc.), or HAVING clauses, use salesforce_aggregate_query instead. Examples: 1. Parent-to-child query (e.g., Account with Contacts): - objectName:. It is categorised as a Read tool in the Salesforce MCP Server MCP Server, which means it retrieves data without modifying state.
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 Read tool with low risk. Read-only tools are generally safe to allow by default.
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 (tsmztech/mcp-server-salesforce). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Salesforce MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 Salesforce MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.