Search site preferences by name, description, or type. Use to validate preference names and types when working with Site.getCurrent().getCustomPreferenceValue() or dw.system.Site.current.preferences.custom.*.
AI agents call search_site_preferences to retrieve information from Sfcc Dev without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only query tool for retrieving and validating Salesforce Commerce Cloud site preference metadata. It retrieves information to assist developers in understanding available preferences but does not create, modify, delete, or execute operations. The blast radius of misuse is minimal—an AI agent could only retrieve preference information already accessible to the development environment.
From the tool's definition Tool performs search/query operations on site preferences—'Search site preferences by name, description, or type'—with no data modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search site preferences by name, description, or type. Use to validate preference names and types when working with Site.getCurrent().getCustomPreferenceValue() or dw.system.Site.current.preferences.custom.*. It is categorised as a Read tool in the Sfcc Dev MCP Server, which means it retrieves data without modifying state.
Register the Sfcc Dev MCP server in PolicyLayer and add a rule for search_site_preferences: 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 Sfcc Dev. Nothing to install.
search_site_preferences is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_site_preferences 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 search_site_preferences. 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.
search_site_preferences is provided by the Sfcc Dev MCP server (sfcc-dev-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →