open_record

THE RISK

High Risk

Why open_record needs a policy

This tool triggers a browser action (opening a URL/record in a browser), which is an external operation. It does not read, write, or delete data itself, but it executes a browser-side action. The blast radius is low since it merely opens a view of a record without modifying anything.

From the tool's definition Opens a Salesforce record in a browser

Documented attack patterns abuse exactly the kind of access open_record gives an agent:

POLICY

How to control open_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 open_record:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "open_record": {
      "limits": [
        {
          "counter": "open_record_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

open_record stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. 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.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Salesforce MCP Server tools

Destructive clear_default_org Clear the default target org from the Salesforce CLI configuration. After clearing, all to Destructive delete_record Delete a record from a Salesforce org using the REST API. Permanently removes the specifie Destructive package_uninstall Uninstall a second-generation package from the target org. Specify the package ID (starts Destructive logout Log out of a Salesforce org. Use targetOrg to logout of a specific org, or set all to true Execute deploy_start Deploy metadata to Salesforce org with test execution options. Execute execute_anonymous_apex Execute Apex code in a Salesforce Org. This command allows you to run Apex code directly a Execute run_apex_tests Run Apex tests in a Salesforce Org. This command allows you to execute unit tests with var Execute run_code_analyzer Analyze code for quality and security issues. Run list_code_analyzer_rules first to select

All 41 Salesforce MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Salesforce MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about open_record

What does the open_record tool do? +

Opens a Salesforce record in a browser. It is categorised as a Execute tool in the Salesforce MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on open_record? +

Register the Salesforce MCP Server MCP server in PolicyLayer and add a rule for open_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 open_record? +

open_record is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit open_record? +

Yes. Add a rate_limit block to the open_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 open_record completely? +

Set action: deny in the PolicyLayer policy for open_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 open_record? +

open_record 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.

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 →