sf_assign_territory_to_user

SERVERSalesforce Metadata Mcp SOURCEsalesforce-metadata-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-assign-territory-to-user.md

WHAT IT DOES

What sf_assign_territory_to_user does on Salesforce Metadata Mcp

AI agents use sf_assign_territory_to_user to create or update resources in Salesforce Metadata Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Salesforce Metadata Mcp environment.

RISK

Why sf_assign_territory_to_user is rated Medium

This tool creates or modifies a UserTerritory2Association record, which is a write operation. It is reversible (the assignment can be removed), so it is not Destructive. The blast radius is high because incorrect territory assignments could grant visibility into sensitive accounts to unintended users, or revoke visibility from legitimate users, affecting sales operations and data access controls.

From the tool's definition Tool description states it 'Assigns a user to an Enterprise Territory Management territory via the UserTerritory2Association SObject.' The parameters include username/userId and territoryName, indicating the tool creates or modifies the association record.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sf_assign_territory_to_user safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Salesforce Metadata Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sf_assign_territory_to_user, this is the rule to start with:

sf_assign_territory_to_user Rate-limited

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

View as policy code

policy.json

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

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Salesforce Metadata Mcp, apply this rule, and every sf_assign_territory_to_user call is checked against it from then on.

FAQ

Questions about sf_assign_territory_to_user

What does the sf_assign_territory_to_user tool do? +

Assigns a user to an Enterprise Territory Management territory via the UserTerritory2Association SObject. Users assigned to a territory get visibility into accounts in that territory. username or userId: identify the user territoryName: DeveloperName of the Territory2 to assign roleInTerritory: optional role —. It is categorised as a Write tool in the Salesforce Metadata Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on sf_assign_territory_to_user? +

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

What risk level is sf_assign_territory_to_user? +

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

Can I rate-limit sf_assign_territory_to_user? +

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

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

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

KEEP EXPLORING

More on Salesforce Metadata, and thousands of servers like it.

This server

All 213 Salesforce Metadata tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →