Scan all Claude Code conversation files for oversized images that cause API errors. Returns detailed report of issues found without making changes.
AI agents call scan_image_issues to retrieve information from Claude Code Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a diagnostic scan of conversation files to identify oversized images causing API errors. It retrieves and analyzes data (scan results) but makes no modifications, deletions, or state changes. The tool is purely informational/observational, fitting the Read category for data retrieval with no side effects.
From the tool's definition Tool description explicitly states 'Returns detailed report of issues found without making changes.' The scan operation is read-only and observational in nature.
Documented attack patterns abuse exactly the kind of access scan_image_issues gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Code Toolkit, and nothing reaches the server without passing your rules. This is the rule we recommend for scan_image_issues:
{
"version": "1",
"default": "deny",
"tools": {
"scan_image_issues": {}
}
} scan_image_issues is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Scan all Claude Code conversation files for oversized images that cause API errors. Returns detailed report of issues found without making changes. It is categorised as a Read tool in the Claude Code Toolkit MCP Server, which means it retrieves data without modifying state.
Register the Claude Code Toolkit MCP server in PolicyLayer and add a rule for scan_image_issues: 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 Claude Code Toolkit. Nothing to install.
scan_image_issues 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 scan_image_issues 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 scan_image_issues. 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.
scan_image_issues is provided by the Claude Code Toolkit MCP server (asifkibria/claude-code-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Code Toolkit, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
40 Claude Code Toolkit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.