Authenticate and login to a Salesforce org via web browser. This command opens a browser window for OAuth authentication flow, allowing you to securely connect to a Salesforce org. After successful authentication, the org credentials are stored locally by the Salesforce CLI for future use. Use is...
AI agents use login_into_org to create or update resources in Salesforce MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Salesforce MCP Server environment.
This tool creates and stores new org connection credentials, which is a reversible write operation that modifies local authentication state. While it involves authentication, the core action is writing/storing credentials for future use. It is not destructive (credentials can be removed), not financial, and not execute-on-data (though it enables future operations).
From the tool's definition Tool description states it 'opens a browser window for OAuth authentication flow' and 'org credentials are stored locally by the Salesforce CLI for future use.' This creates and persists a new authentication credential/connection (a write operation),…
Documented attack patterns abuse exactly the kind of access login_into_org gives an agent:
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 login_into_org:
{
"version": "1",
"default": "deny",
"tools": {
"login_into_org": {
"limits": [
{
"counter": "login_into_org_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}login_into_org stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Authenticate and login to a Salesforce org via web browser. This command opens a browser window for OAuth authentication flow, allowing you to securely connect to a Salesforce org. After successful authentication, the org credentials are stored locally by the Salesforce CLI for future use. Use isProduction=true for production/developer orgs (login.salesforce.com) or isProduction=false for sandboxes/scratch orgs (test.salesforce.com). The alias parameter creates a convenient shorthand name for accessing this org in subsequent commands. IMPORTANT: This tool requires both. It is categorised as a Write tool in the Salesforce MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Salesforce MCP Server MCP server in PolicyLayer and add a rule for login_into_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 MCP Server. Nothing to install.
login_into_org is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the login_into_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.
Set action: deny in the PolicyLayer policy for login_into_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.
login_into_org 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.
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.
Free to start. No card required.
41 Salesforce MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.