Search for text across multiple Salesforce objects simultaneously from a project. USE THIS TOOL when searching for records that mention, contain, or reference specific text (like company names, keywords, phrases) across different objects. This is the PRIMARY tool for text-based searches across yo...
AI agents call search_records to retrieve information from Salesforce CLI 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 a read-only search operation across Salesforce objects. It retrieves or queries data without side effects—no data is created, modified, deleted, or executed. The misuse risk is low: an AI agent searching records cannot cause financial harm, delete data, or execute arbitrary code.
From the tool's definition Tool name 'search_records' and description explicitly states 'Search for text across multiple Salesforce objects' and 'This is the PRIMARY tool for text-based searches'.
Attacks that exploit this kind of access
Search for text across multiple Salesforce objects simultaneously from a project. USE THIS TOOL when searching for records that mention, contain, or reference specific text (like company names, keywords, phrases) across different objects. This is the PRIMARY tool for text-based searches across your org - it. It is categorised as a Read tool in the Salesforce CLI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Salesforce CLI MCP Server MCP server in PolicyLayer and add a rule for search_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 CLI MCP Server. Nothing to install.
search_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 search_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 search_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.
search_records is provided by the Salesforce CLI MCP Server MCP server (perrynet/salesforce-cli-mcp-server). 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 →