sf_assign_layout_to_record_type
Assigns an existing page layout to a specific record type on an object by updating the Profile metadata. Controls which page layout users see when viewing records of a given record type. objectName: the API name of the object recordTypeName: developer name of the record type layoutName: full name...
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-assign-layout-to-record-type.md
What sf_assign_layout_to_record_type does on Salesforce Metadata Mcp
AI agents use sf_assign_layout_to_record_type 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_assign_layout_to_record_type is rated Medium
This tool modifies Salesforce metadata by updating Profile configurations to change which page layout is displayed for a record type. This is a reversible change to configuration data (metadata update), making it a Write operation.
From the tool's definition Assigns an existing page layout to a specific record type...by updating the Profile metadata. Controls which page layout users see when viewing records of a given record type.
Attacks that exploit this kind of access
The rule that runs sf_assign_layout_to_record_type 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_layout_to_record_type, this is the rule to start with:
sf_assign_layout_to_record_type 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_assign_layout_to_record_type call is checked against it from then on.
Questions about sf_assign_layout_to_record_type
Assigns an existing page layout to a specific record type on an object by updating the Profile metadata. Controls which page layout users see when viewing records of a given record type. objectName: the API name of the object recordTypeName: developer name of the record type layoutName: full name of the page layout, 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_assign_layout_to_record_type: 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_assign_layout_to_record_type 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_assign_layout_to_record_type 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_assign_layout_to_record_type. 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_assign_layout_to_record_type 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