Inspect a cutout or transparent PNG for edge quality and cleanup needs.
AI agents call inspect_cutout to retrieve information from Jgkme/kilo Image Gen without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The verb 'inspect' and the focus on analyzing 'edge quality and cleanup needs' suggest this tool performs image analysis or quality assessment. It retrieves information about image characteristics (edge quality) but does not create, modify, delete, or execute external operations. This is a Read operation with minimal blast radius.
From the tool's definition Tool name 'inspect_cutout' and description 'Inspect a cutout or transparent PNG for edge quality and cleanup needs' indicate the tool only examines or analyzes image properties without modifying data.
Attacks that exploit this kind of access
Inspect a cutout or transparent PNG for edge quality and cleanup needs. It is categorised as a Read tool in the Jgkme/kilo Image Gen MCP Server, which means it retrieves data without modifying state.
Register the Jgkme/kilo Image Gen MCP server in PolicyLayer and add a rule for inspect_cutout: 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 Jgkme/kilo Image Gen. Nothing to install.
inspect_cutout 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 inspect_cutout 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 inspect_cutout. 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.
inspect_cutout is provided by the Jgkme/kilo Image Gen MCP server (jgkme/img-gen-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 →