get_store
Get one verified Booyah store by stable id ("store_1") or slug, with a capped list of its published products. Use after search_products to see everything a seller offers.
This record as markdown: /tools/com-getbooyah-booyah-index/get-store.md
What get_store does on Booyah Index
AI agents call get_store to retrieve information from Booyah Index 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 |
|---|---|---|---|
id | string | Yes | Store id ("store_1") or slug ("booyah") |
limit | number | — | Max products returned, 1-50 (default 20) |
language | string | — |
Parameters from the server's own tool schema.
Why get_store is rated Low
Even though get_store only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_store safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Booyah Index, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_store, this is the rule to start with:
get_store 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 Booyah Index, apply this rule, and every get_store call is checked against it from then on.
Questions about get_store
Get one verified Booyah store by stable id ("store_1") or slug, with a capped list of its published products. Use after search_products to see everything a seller offers. It is categorised as a Read tool in the Booyah Index MCP Server, which means it retrieves data without modifying state.
get_store accepts 3 parameters: id, limit, language. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Booyah Index MCP server in PolicyLayer and add a rule for get_store: 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 Booyah Index. Nothing to install.
get_store 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 get_store 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 get_store. 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.
get_store is provided by the Booyah Index MCP server (https://getbooyah.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Booyah Index, and thousands of servers like it.
This server
Across the catalogue