AI agents call get_job_log_entries 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 retrieves and queries existing job log data filtered by severity level (error/warn/info/debug/all). It has no side effects, does not execute code, modify data, delete records, or trigger external operations. It is purely informational and diagnostic in nature, fitting the Read category.
From the tool's definition Tool description explicitly states 'Get job log entries' with filtering by level—a retrieval operation with no modification, creation, deletion, or execution capability. The verb 'get' and the context of reading log entries confirms read-only access.
Attacks that exploit this kind of access
Get job log entries by level (error/warn/info/debug/all). Unlike standard logs, job logs combine all levels in one file. 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_log_entries: 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_log_entries 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_log_entries 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_log_entries. 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_log_entries 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 →