Check the status of a reels creation job. Returns progress (0-100),
AI agents call check_job_status to retrieve information from SoManyLemons MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the status of an existing job and returns progress metadata. It is a read-only operation with no side effects, no data modification, no code execution, and no irreversible actions. The low severity reflects minimal blast radius—an AI agent misusing this tool could only repeatedly check status, wasting resources at worst.
From the tool's definition Tool name 'check_job_status' and description 'Check the status of a reels creation job. Returns progress (0-100)' indicate a query operation that retrieves status information without modifying or executing any operations.
Attacks that exploit this kind of access
Check the status of a reels creation job. Returns progress (0-100),. It is categorised as a Read tool in the SoManyLemons MCP MCP Server, which means it retrieves data without modifying state.
Register the SoManyLemons MCP server in PolicyLayer and add a rule for check_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 SoManyLemons MCP. Nothing to install.
check_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 check_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 check_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.
check_job_status is provided by the SoManyLemons MCP server (nomiddleinc/somanylemons-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 →