sf_create_role_hierarchy
Creates multiple Salesforce roles in the role hierarchy in a single call. Roles control record visibility — users in higher roles see records owned by subordinate-role users (depending on OWD settings). Use to set up an entire hierarchy at once. roles: array of {fullName, name, parentRole?, descr...
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-create-role-hierarchy.md
What sf_create_role_hierarchy does on Salesforce Metadata Mcp
AI agents use sf_create_role_hierarchy 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.
Why sf_create_role_hierarchy is rated Medium
This tool creates new roles that fundamentally control data visibility and user access permissions across Salesforce. While the operation is technically reversible (roles can be deleted), the blast radius is high because misconfigured role hierarchies can expose sensitive records to unintended users or restrict legitimate access.
From the tool's definition Tool name contains 'create' and description states 'Creates multiple Salesforce roles in the role hierarchy in a single call.' The action is reversible (roles can be deleted or modified later) but has significant organizational impact by controlling record…
Attacks that exploit this kind of access
The rule that runs sf_create_role_hierarchy 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_create_role_hierarchy, this is the rule to start with:
sf_create_role_hierarchy 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Salesforce Metadata Mcp, apply this rule, and every sf_create_role_hierarchy call is checked against it from then on.
Questions about sf_create_role_hierarchy
Creates multiple Salesforce roles in the role hierarchy in a single call. Roles control record visibility — users in higher roles see records owned by subordinate-role users (depending on OWD settings). Use to set up an entire hierarchy at once. roles: array of {fullName, name, parentRole?, description?} - fullName: role API name (e.g. 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.
Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_create_role_hierarchy: 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.
sf_create_role_hierarchy 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 sf_create_role_hierarchy 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 sf_create_role_hierarchy. 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.
sf_create_role_hierarchy 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.
More on Salesforce Metadata, and thousands of servers like it.
This server
Across the catalogue