view_image
Fetch a rendered Framesail image so you (and your user) can SEE it — pass a URL from get_segment_assets, get_style, or asset endpoints. Returns the image inline. Only Framesail media URLs are allowed.
This record as markdown: /tools/com-framesail-framesail/view-image.md
What view_image does on Framesail
AI agents call view_image to retrieve information from Framesail without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Public Framesail media URL to fetch — a public_url from get_segment_assets, a file_path from list_assets, or a template/preset image URL from get_style / list_s |
Parameters from the server's own tool schema.
Why view_image is rated Low
This tool retrieves and displays image data without creating, modifying, deleting, executing code, or committing financial transactions. It is a simple read operation constrained to Framesail media URLs, posing minimal security risk.
From the tool's definition Tool name 'view_image' and description explicitly states it 'Fetch[es] a rendered Framesail image' with 'Returns the image inline.' The operation is read-only and retrieves already-rendered media without modification.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs view_image safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Framesail, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For view_image, this is the rule to start with:
view_image 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 Framesail, apply this rule, and every view_image call is checked against it from then on.
Questions about view_image
Fetch a rendered Framesail image so you (and your user) can SEE it — pass a URL from get_segment_assets, get_style, or asset endpoints. Returns the image inline. Only Framesail media URLs are allowed. It is categorised as a Read tool in the Framesail MCP Server, which means it retrieves data without modifying state.
view_image accepts 1 parameter: url. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the Framesail MCP server in PolicyLayer and add a rule for view_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 Framesail. Nothing to install.
view_image 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 view_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 view_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.
view_image is provided by the Framesail MCP server (https://api.framesail.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Framesail, and thousands of servers like it.
This server
Across the catalogue