AI agents use manage_image to create or update resources in OCR-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OCR-MCP environment.
Without a description, classification relies on naming convention and server context. 'manage_image' most likely creates, modifies, or organizes image data within the OCR pipeline, fitting the Write category (reversible changes). Severity is medium because image manipulation could affect document processing integrity, but lacks the irreversibility of Destructive operations or the external execution risk of Execute.
From the tool's definition Tool name 'manage_image' implies image data manipulation; sibling tools 'process_document' and 'operate_scanner' suggest document/image workflows. The tool name prefix 'manage' typically indicates create/modify operations.
Documented attack patterns abuse exactly the kind of access manage_image gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OCR-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for manage_image:
{
"version": "1",
"default": "deny",
"tools": {
"manage_image": {
"limits": [
{
"counter": "manage_image_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}manage_image stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
manage_image. It is categorised as a Write tool in the OCR-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OCR- MCP server in PolicyLayer and add a rule for manage_image: 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 OCR-MCP. Nothing to install.
manage_image is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the manage_image 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 manage_image. 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.
manage_image is provided by the OCR- MCP server (sandraschi/ocr-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OCR-MCP, 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.
8 OCR-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.