AI agents call get_local_image_size to retrieve information from Image Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves image dimensions from a local file—a pure data retrieval operation with no side effects. It does not create, modify, delete, execute code, or involve financial transactions. It falls squarely into the Read category with low severity due to minimal blast radius if misused.
From the tool's definition Tool name 'get_local_image_size' and description 'Get the size of a local image' indicate a read-only query operation that retrieves metadata (width, height) without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access get_local_image_size gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Image Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for get_local_image_size:
{
"version": "1",
"default": "deny",
"tools": {
"get_local_image_size": {}
}
}get_local_image_size 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.
Get the size of a local image. It is categorised as a Read tool in the Image Tools MCP Server, which means it retrieves data without modifying state.
Register the Image Tools MCP server in PolicyLayer and add a rule for get_local_image_size: 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 Image Tools. Nothing to install.
get_local_image_size 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 get_local_image_size 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 get_local_image_size. 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.
get_local_image_size is provided by the Image Tools MCP server (kshern/image-tools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Image Tools, 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.
5 Image Tools tools catalogued and risk-classified — across an index of 43,000+ MCP servers.