AI agents call get_sfra_categories 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 metadata about SFRA documentation structure and returns category information. It has no side effects, does not modify data, execute code, delete resources, or involve financial transactions. It is purely informational, making it a Read operation with low severity—misuse would only retrieve documentation structure information without risk to systems or data.
From the tool's definition Tool description states 'Get all SFRA document categories with counts' — a retrieval operation with no modification or execution. The verb 'Get' and the action of browsing/understanding documentation are read-only.
Attacks that exploit this kind of access
Get all SFRA document categories with counts. Use to understand documentation organization before browsing. 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_categories: 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_categories 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_categories 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_categories. 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_categories 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 →