Get image outputs from a specific cell by its index Args: index: The index of the cell to get images from Returns: A list of images from the cell output
AI agents call get_image_output to retrieve information from JupyterMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves pre-existing image outputs from notebook cell execution results. It performs no side effects, executes no code, and modifies nothing. It is purely a data retrieval operation with minimal blast radius—an AI agent calling this tool cannot cause harm beyond accessing what already exists in the notebook. Classification as Read with low severity is appropriate.
From the tool's definition Tool name is 'get_image_output' and description states 'Get image outputs from a specific cell'. The verb 'Get' and the return of existing outputs (not creating, modifying, executing, or deleting data) clearly indicate a read operation.
Documented attack patterns abuse exactly the kind of access get_image_output gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JupyterMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_image_output:
{
"version": "1",
"default": "deny",
"tools": {
"get_image_output": {}
}
}get_image_output 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 image outputs from a specific cell by its index Args: index: The index of the cell to get images from Returns: A list of images from the cell output. It is categorised as a Read tool in the JupyterMCP MCP Server, which means it retrieves data without modifying state.
Register the Jupyter MCP server in PolicyLayer and add a rule for get_image_output: 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 JupyterMCP. Nothing to install.
get_image_output 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_image_output 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_image_output. 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_image_output is provided by the Jupyter MCP server (jjsantos01/jupyter-notebook-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from JupyterMCP, 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.
11 JupyterMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.