Query records from a SINGLE Salesforce object using structured field conditions. Use this for precise queries on ONE object with specific field criteria (e.g., Status =
AI agents call 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 performs data retrieval only—querying Salesforce records based on field criteria. The description explicitly indicates querying/retrieving data with no mention of creating, modifying, deleting, or executing code. This is a standard Read operation.
From the tool's definition Tool name 'query_records' and description states it 'Query records from a SINGLE Salesforce object' with 'field conditions' and 'precise queries' on structured data retrieval without modification capability indicated.
Documented attack patterns abuse exactly the kind of access 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 query_records:
{
"version": "1",
"default": "deny",
"tools": {
"query_records": {}
}
} 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 a SINGLE Salesforce object using structured field conditions. Use this for precise queries on ONE object with specific field criteria (e.g., Status =. 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 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.
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 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 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.
query_records is provided by the Salesforce MCP Server MCP server (advancedcommunities/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.
41 Salesforce MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.