AI agents call get_isml_element 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 ISML (Salesforce templating language) elements. It performs a lookup operation to fetch information, which is characteristic of a Read category tool. There are no modifications, deletions, code execution, or financial implications. The low severity reflects that documentation retrieval cannot harm the system or data.
From the tool's definition Tool name is 'get_isml_element' and description states it retrieves 'detailed documentation for an ISML element including syntax, attributes, examples, and use cases.' The verb 'Get' and the action of retrieving documentation indicate a read-only query…
Attacks that exploit this kind of access
Get detailed documentation for an ISML element including syntax, attributes, examples, and use cases. 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_isml_element: 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_isml_element 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_isml_element 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_isml_element. 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_isml_element 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 →