Search for records across multiple Salesforce objects
AI agents call search_records to retrieve information from MCP Salesforce Lite 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 data across Salesforce objects without modifying, deleting, or executing external operations. However, severity is elevated to medium rather than low because searching across multiple objects in a CRM system could expose sensitive customer, financial, or proprietary business data if an AI agent performs overly broad searches or lacks appropriate access controls.
From the tool's definition Tool name 'search_records' and description 'Search for records across multiple Salesforce objects' indicate querying/retrieval functionality with no side effects mentioned. Classified as Read operation.
Attacks that exploit this kind of access
Search for records across multiple Salesforce objects. It is categorised as a Read tool in the MCP Salesforce Lite MCP Server, which means it retrieves data without modifying state.
Register the MCP Salesforce Lite 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 MCP Salesforce Lite. 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 MCP Salesforce Lite MCP server (luvl/mcp-salesforce-lite). 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 →