High Risk →

open_org

Open a Salesforce org in the browser

Risk signalsOpens authenticated session in browser

Part of the Salesforce server.

open_org can trigger actions in Salesforce, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE SALESFORCE →

Free to start. No card required.

AI agents invoke open_org to trigger processes or run actions in Salesforce. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

open_org can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "open_org": {
      "limits": [
        {
          "counter": "open_org_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Salesforce policy for all 35 tools.

Get this rule live on your own Salesforce server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY SALESFORCE →

View all 35 tools →

These attack patterns abuse exactly the kind of access open_org gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so open_org only ever does what you allow.

SECURE SALESFORCE →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the open_org tool do? +

Open a Salesforce org in the browser. It is categorised as a Execute tool in the Salesforce 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_org? +

Register the Salesforce MCP server in PolicyLayer and add a rule for open_org: 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. Nothing to install.

What risk level is open_org? +

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

Can I rate-limit open_org? +

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

Set action: deny in the PolicyLayer policy for open_org. 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_org? +

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

Enforce policy on every Salesforce tool call.

Deterministic rules across all 35 Salesforce tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.