openbrewery.breweries.search
Search breweries by name with partial, case-insensitive matching. Returns name, address, geo-coordinates, phone, and website for each match (Open Brewery DB)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/openbrewery.breweries.search.md
What openbrewery.breweries.search does on Apibase
AI agents call openbrewery.breweries.search 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 |
|---|---|---|---|
page | integer | — | Page number for pagination (default 1). |
query | string | Yes | Search term matched against brewery names (partial, case-insensitive). |
per_page | integer | — | Results per page (default 50, max 200). |
Parameters from the server's own tool schema.
Why openbrewery.breweries.search is rated Low
Queries brewery data without modifying state or executing operations. Purely informational retrieval.
From the tool's definition Search breweries by name with partial, case-insensitive matching. Returns name, address, geo-coordinates, phone, and website.
Attacks that exploit this kind of access
The rule that runs openbrewery.breweries.search 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 openbrewery.breweries.search, this is the rule to start with:
openbrewery.breweries.search 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 openbrewery.breweries.search call is checked against it from then on.
Questions about openbrewery.breweries.search
Search breweries by name with partial, case-insensitive matching. Returns name, address, geo-coordinates, phone, and website for each match (Open Brewery DB). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
openbrewery.breweries.search accepts 3 parameters: page, query, per_page. Required: query. 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 openbrewery.breweries.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 Apibase. Nothing to install.
openbrewery.breweries.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 openbrewery.breweries.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 openbrewery.breweries.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.
openbrewery.breweries.search 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