AI agents use gyazo_upload to create or update resources in Gyazo MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gyazo MCP Server environment.
Uploading an image is a reversible write operation that creates a new resource. It does not execute arbitrary code, delete data, or move money. The severity is medium because unauthorized uploads could fill storage, create unwanted public images, or leak sensitive image content, but the action itself is not irreversible (uploaded images can typically be deleted) and does not have cascading system effects like code…
From the tool's definition Tool name is 'gyazo_upload' and description states 'Upload an image to Gyazo' — this creates new data (an image resource) in the Gyazo service.
Documented attack patterns abuse exactly the kind of access gyazo_upload gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gyazo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for gyazo_upload:
{
"version": "1",
"default": "deny",
"tools": {
"gyazo_upload": {
"limits": [
{
"counter": "gyazo_upload_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}gyazo_upload stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Upload an image to Gyazo. It is categorised as a Write tool in the Gyazo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gyazo MCP Server MCP server in PolicyLayer and add a rule for gyazo_upload: 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 Gyazo MCP Server. Nothing to install.
gyazo_upload is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gyazo_upload 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 gyazo_upload. 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.
gyazo_upload is provided by the Gyazo MCP Server MCP server (nota/gyazo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gyazo MCP Server, 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.
4 Gyazo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.