search.google.images
Google Image search results — image URL, thumbnail, dimensions, source domain. Search any visual content worldwide (Serper.dev)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/search.google.images.md
What search.google.images does on Apibase
AI agents call search.google.images to retrieve information from Apibase 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 |
|---|---|---|---|
q | string | Yes | Image search query (e.g. "golden gate bridge sunset") |
gl | string | — | Country code (e.g. "us") |
num | integer | — | Number of images (default 10, max 100) |
Parameters from the server's own tool schema.
Why search.google.images is rated Low
Retrieves image search metadata with no data modification or execution capabilities.
From the tool's definition Search results — image URL, thumbnail, dimensions, source domain
Attacks that exploit this kind of access
The rule that runs search.google.images safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search.google.images, this is the rule to start with:
search.google.images 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 Apibase, apply this rule, and every search.google.images call is checked against it from then on.
Questions about search.google.images
Google Image search results — image URL, thumbnail, dimensions, source domain. Search any visual content worldwide (Serper.dev). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
search.google.images accepts 3 parameters: q, gl, num. Required: q. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for search.google.images: 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 Apibase. Nothing to install.
search.google.images 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 search.google.images 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 search.google.images. 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.
search.google.images is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue