AI agents call search_job_logs_by_name 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 performs a search/query operation to retrieve job log files based on job name matching. It has no side effects, does not execute code, does not modify data, and does not delete anything. It is a read-only diagnostic tool consistent with the server's purpose of development assistance and debugging.
From the tool's definition Tool description states 'Find job log files by job name' and 'Use to locate logs for a specific job.' The verb 'find' and 'locate' indicate retrieval/querying operations with no modification or execution capability.
Attacks that exploit this kind of access
Find job log files by job name (partial match supported). Use to locate logs for a specific job. 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_by_name: 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_by_name 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_by_name 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_by_name. 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_by_name 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 →