image_save_from_buffer

Save image from binary data (base64 string or buffer) to local file system. Useful for saving images received from other APIs or services. All paths are relative to the project root.

Server TSCodex MCP Images unbywyd/tscodex-mcp-images
Category Write
Risk class Medium
Parameters 00 required

What image_save_from_buffer does on TSCodex MCP Images

AI agents use image_save_from_buffer to create or update resources in TSCodex MCP Images — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TSCodex MCP Images environment.

Why image_save_from_buffer needs a policy

The tool writes image files to the local file system based on provided binary data. While not destructive (existing files are not explicitly overwritten or deleted), it creates new files and could consume disk space or overwrite existing files if paths collide. The 'All paths are relative to the project root' indicates the operation affects the local filesystem with user-controlled paths.

From the tool's definition Tool description states it 'Save[s] image from binary data... to local file system.' This is a create/write operation that persists data to disk.

Risk signalsAdmin/system-level operation

Questions about image_save_from_buffer

What does the image_save_from_buffer tool do? +

Save image from binary data (base64 string or buffer) to local file system. Useful for saving images received from other APIs or services. All paths are relative to the project root. It is categorised as a Write tool in the TSCodex MCP Images MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on image_save_from_buffer? +

Register the TSCodex MCP Images MCP server in PolicyLayer and add a rule for image_save_from_buffer: 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 TSCodex MCP Images. Nothing to install.

What risk level is image_save_from_buffer? +

image_save_from_buffer is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit image_save_from_buffer? +

Yes. Add a rate_limit block to the image_save_from_buffer 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.

How do I block image_save_from_buffer completely? +

Set action: deny in the PolicyLayer policy for image_save_from_buffer. 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.

What MCP server provides image_save_from_buffer? +

image_save_from_buffer is provided by the TSCodex MCP Images MCP server (unbywyd/tscodex-mcp-images). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.