get-record

THE RISK

Low Risk

Why get-record needs a policy

This tool retrieves data from Salesforce by record ID with optional field filtering. It is a query operation with no capability to create, modify, delete, or execute code. The 'optional field selection' parameter further confirms this is a safe read operation.

From the tool's definition Tool name 'get-record' and description 'Retrieve a record by ID with optional field selection' indicate a read-only operation that fetches existing data without modification or side effects.

Documented attack patterns abuse exactly the kind of access get-record gives an agent:

POLICY

How to control get-record

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 get-record:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-record": {}
  }
}

get-record is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Salesforce MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Salesforce MCP Server tools

Destructive delete-record Delete records by ID(s) with auto-bulk switching Execute deploy-bundle Deploy a metadata bundle (e.g., LWC) from a directory path Execute deploy-metadata Deploy metadata components to Salesforce org Execute execute-apex Execute anonymous Apex code with debug log capture Execute execute-soql Execute SOQL query with auto-bulk switching for large result sets Execute execute-sosl Execute SOSL search with multi-object support Execute run-apex-tests Run Apex tests with coverage and detailed results Write create-record Create single or multiple records with auto-bulk switching

All 17 Salesforce MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get-record

What does the get-record tool do? +

Retrieve a record by ID with optional field selection. It is categorised as a Read tool in the Salesforce MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-record? +

Register the Salesforce MCP Server 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 Salesforce MCP Server. Nothing to install.

What risk level is get-record? +

get-record is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-record? +

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.

How do I block get-record completely? +

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.

What MCP server provides get-record? +

get-record is provided by the Salesforce MCP Server MCP server (jaworjar95/salesforce-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Salesforce MCP Server tool call.

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.

CHECK YOUR STACK →