This record as markdown: /tools/io-github-heznpc-iconnect/get-photo-info.md
What get_photo_info does on Iconnect
AI agents call get_photo_info to retrieve information from Iconnect without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_photo_info is rated Low
This tool retrieves photo metadata without side effects. It is a query operation that does not create, modify, delete, or execute actions. The minimal severity reflects that metadata disclosure alone poses limited risk unless the metadata itself contains highly sensitive information, which is unlikely for standard photo attributes.
From the tool's definition Tool name and description clearly indicate retrieval of metadata: 'Get detailed metadata for a specific photo by ID.' No modification, deletion, or execution capabilities are described.
Attacks that exploit this kind of access
The rule that runs get_photo_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_photo_info, this is the rule to start with:
get_photo_info 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 Iconnect, apply this rule, and every get_photo_info call is checked against it from then on.
Questions about get_photo_info
Get detailed metadata for a specific photo by ID. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.
Register the Iconnect MCP server in PolicyLayer and add a rule for get_photo_info: 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 Iconnect. Nothing to install.
get_photo_info 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_photo_info 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_photo_info. 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_photo_info is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue