AI agents call get_sfra_documents_by_category 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 tool queries and returns documentation about Salesforce B2C Commerce Cloud SFRA (Storefront Reference Architecture) organized by category. It performs a read-only operation to fetch development reference materials. There is no indication of data modification, code execution, deletion, or financial operations.
From the tool's definition The tool 'get_sfra_documents_by_category' retrieves SFRA documents filtered by functional area. The verb 'get' and description 'filtered by functional area' indicate data retrieval without modification or side effects.
Attacks that exploit this kind of access
Get SFRA documents filtered by functional area (core classes, product models, order/cart, customer, pricing, store). 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 get_sfra_documents_by_category: 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.
get_sfra_documents_by_category 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 get_sfra_documents_by_category 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 get_sfra_documents_by_category. 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.
get_sfra_documents_by_category 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 →