Full-text search for captures uploaded by users on Gyazo
AI agents call gyazo_search to retrieve information from Gyazo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing screenshot/image data from Gyazo without creating, modifying, or deleting anything. It is clearly a Read operation. Severity is medium rather than low because search results could expose sensitive information captured in screenshots (PII, credentials, proprietary data) if an AI agent performs broad searches, though the blast radius depends on what users have uploaded and the…
From the tool's definition Tool performs 'Full-text search for captures uploaded by users on Gyazo' — a retrieval operation with no modification or execution capability. The verb 'search' and functional purpose indicate data querying.
Documented attack patterns abuse exactly the kind of access gyazo_search 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_search:
{
"version": "1",
"default": "deny",
"tools": {
"gyazo_search": {}
}
}gyazo_search 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.
Full-text search for captures uploaded by users on Gyazo. It is categorised as a Read tool in the Gyazo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Gyazo MCP Server MCP server in PolicyLayer and add a rule for gyazo_search: 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_search 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 gyazo_search 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_search. 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_search 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.