Retrieve a specific Salesforce record by ID with limit and pagination
AI agents call get_record 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 performs a read-only operation that queries and returns data from Salesforce CRM by record ID. It has no side effects—it does not create, modify, delete, or execute any operations. The mention of 'limit and pagination' further confirms it is a retrieval mechanism. Even in a security context, an AI agent misusing this tool could only expose existing data, making the blast radius low.
From the tool's definition Tool name 'get_record' and description 'Retrieve a specific Salesforce record by ID with limit and pagination' indicate data retrieval without modification or deletion.
Attacks that exploit this kind of access
Retrieve a specific Salesforce record by ID with limit and pagination. 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 get_record: 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.
get_record 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 get_record 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 get_record. 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.
get_record 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 →