assign_permission_set

THE RISK

Medium Risk

Why assign_permission_set needs a policy

This tool creates or modifies access control configurations by assigning permission sets to users. While it does not delete data or move money, permission set assignment is a Write operation that changes user entitlements and org security posture.

From the tool's definition Assign a permission set to one or more org users. This modifies user access permissions within the Salesforce org, granting rights and capabilities to users.

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

POLICY

How to control assign_permission_set

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 assign_permission_set:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "assign_permission_set": {
      "limits": [
        {
          "counter": "assign_permission_set_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

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.

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 →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about assign_permission_set

What does the assign_permission_set tool do? +

Assign a permission set to one or more org users. To specify an alias for the --target-org or --on-behalf-of flags, use the CLI username alias, such as the one you set with the. 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.

How do I enforce a policy on assign_permission_set? +

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

assign_permission_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit assign_permission_set? +

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

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

assign_permission_set 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 →