sf_create_search_layout
Creates or updates a SearchLayout for a Salesforce object, defining which fields appear in search results, lookup dialogs, and lookup filter fields. Use to customize what columns users see when they search for records or open a lookup dialog. objectName: the API name of the object, e.g.
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-create-search-layout.md
What sf_create_search_layout does on Salesforce Metadata Mcp
AI agents use sf_create_search_layout 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_search_layout is rated Medium
This tool creates or updates SearchLayout configurations in Salesforce, which modifies metadata that controls UI presentation (search result columns and lookup dialog fields). This is reversible configuration change (the layout can be updated or deleted later), making it Write rather than Execute or Destructive.
From the tool's definition Tool description states it 'Creates or updates a SearchLayout' — explicitly a creation/modification operation. The description uses 'Creates or updates', which is the hallmark of Write-category tools that reversibly modify configuration data.
Attacks that exploit this kind of access
The rule that runs sf_create_search_layout 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_search_layout, this is the rule to start with:
sf_create_search_layout 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_search_layout call is checked against it from then on.
Questions about sf_create_search_layout
Creates or updates a SearchLayout for a Salesforce object, defining which fields appear in search results, lookup dialogs, and lookup filter fields. Use to customize what columns users see when they search for records or open a lookup dialog. objectName: the API name of the object, 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_search_layout: 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_search_layout 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_search_layout 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_search_layout. 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_search_layout 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