AI agents call search_job_logs 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.
The tool queries existing job log data to find patterns and errors. This is a read-only operation used for debugging and monitoring purposes. It retrieves information but does not execute code, modify data, or perform destructive actions. The low severity reflects minimal blast radius if misused by an agent — searching logs cannot corrupt systems or cause unwanted side effects beyond information disclosure.
From the tool's definition Tool description explicitly states it 'Search[es] job logs for patterns, error messages, or custom logging' — a retrieval operation with no modification, execution, or deletion of data.
Attacks that exploit this kind of access
Search job logs for patterns, error messages, or custom logging from job steps. Essential for debugging custom job code. 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_job_logs: 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_job_logs 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_job_logs 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_job_logs. 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_job_logs 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 →