AI agents call get_job_execution_summary 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 only queries and retrieves existing job execution data without modifying, deleting, or triggering any external operations. It is purely informational for debugging and performance monitoring in a development context. There is no risk of data loss, execution of arbitrary code, or external side effects from reading job summaries.
From the tool's definition The tool "Get execution summary for a job" retrieves job metadata (timing, status, error counts, step info) for monitoring purposes. The verb "Get" and use case "monitoring job health and performance" indicate read-only data retrieval with no side effects.
Attacks that exploit this kind of access
Get execution summary for a job: timing, status, error counts, and step info. Use for monitoring job health and performance. 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_job_execution_summary: 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_job_execution_summary 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_job_execution_summary 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_job_execution_summary. 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_job_execution_summary 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 →