get_metainfo
Get metadata information about an image file.
This record as markdown: /tools/sunriseapps-imagesorcery-mcp/get-metainfo.md
What get_metainfo does on πͺ ImageSorcery MCP
AI agents call get_metainfo to retrieve information from πͺ ImageSorcery MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_metainfo is rated Low
This tool queries and retrieves metadata from image files without creating, modifying, or destroying data. It is a straightforward data retrieval operation with no capability to alter state or trigger external actions, making it a Read category tool with low severity.
From the tool's definition Tool name 'get_metainfo' and description 'Get metadata information about an image file' indicate a read-only operation that retrieves metadata without modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_metainfo safely
PolicyLayer is an MCP gateway: it sits between your AI agents and πͺ ImageSorcery MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_metainfo, this is the rule to start with:
get_metainfo is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect πͺ ImageSorcery MCP, apply this rule, and every get_metainfo call is checked against it from then on.
Questions about get_metainfo
Get metadata information about an image file. It is categorised as a Read tool in the πͺ ImageSorcery MCP MCP Server, which means it retrieves data without modifying state.
Register the πͺ ImageSorcery MCP server in PolicyLayer and add a rule for get_metainfo: 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 πͺ ImageSorcery MCP. Nothing to install.
get_metainfo 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_metainfo 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_metainfo. 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_metainfo is provided by the πͺ ImageSorcery MCP server (sunriseapps/imagesorcery-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on πͺ ImageSorcery, and thousands of servers like it.
This server
Across the catalogue