AI agents call search_sfra_documentation 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 documentation search tool that retrieves information from Salesforce SFRA (Storefront Reference Architecture) documentation. It has no side effects, does not execute code, does not modify data, and does not trigger external operations. It is purely informational/read-only access to existing documentation resources, making it a Read category tool with low risk.
From the tool's definition Tool description states 'Search across all SFRA docs' and 'Returns relevance-scored results with categorization.' The verb 'search' combined with 'returns results' indicates querying/retrieving documentation without modifying or executing anything.
Attacks that exploit this kind of access
Search across all SFRA docs for concepts or functionality. Returns relevance-scored results with categorization. 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_sfra_documentation: 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_sfra_documentation 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_sfra_documentation 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_sfra_documentation. 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_sfra_documentation 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 →