查询图片生成状态
AI agents call check_image_status to retrieve information from LiblibAI Picture Generator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the state of an ongoing or completed image generation task. It is a pure read operation that queries data without side effects, modifying content, executing commands, or deleting information. The low severity reflects minimal risk from misuse—checking status cannot harm the system or cause unintended consequences.
From the tool's definition Tool name 'check_image_status' and description '查询图片生成状态' (query image generation status) indicate a status-checking operation with no modification or execution of external operations.
Attacks that exploit this kind of access
查询图片生成状态. It is categorised as a Read tool in the LiblibAI Picture Generator MCP Server, which means it retrieves data without modifying state.
Register the LiblibAI Picture Generator MCP server in PolicyLayer and add a rule for check_image_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 LiblibAI Picture Generator. Nothing to install.
check_image_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_image_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_image_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_image_status is provided by the LiblibAI Picture Generator MCP server (nathansnmmer/picture). 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 →