get-job-status
AI agents call get-job-status to retrieve information from Shopify MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get' prefix strongly indicates a read operation that queries job status without side effects. The empty description lowers confidence slightly, but the naming pattern is consistent with retrieval operations. No capacity to modify, execute code, delete data, or move money is apparent from the name or server context. Classified as Read with low severity due to minimal blast radius if misused by an AI agent.
From the tool's definition Tool named 'get-job-status' with empty description. Based on naming convention, this tool retrieves status information about asynchronous jobs rather than modifying, executing, or deleting data.
Attacks that exploit this kind of access
get-job-status. It is categorised as a Read tool in the Shopify MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Shopify MCP Server MCP server in PolicyLayer and add a rule for get-job-status: 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 Shopify MCP Server. Nothing to install.
get-job-status 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-status 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-status. 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-status is provided by the Shopify MCP Server MCP server (tzenderman/shopify-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 →