get_place
Get the full structured record for one place — any of the 14 Southeast Asian cities — by its Booyah Index slug (from search_places results).
This record as markdown: /tools/com-getbooyah-booyah-index/get-place.md
What get_place does on Booyah Index
AI agents call get_place 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 |
|---|---|---|---|
slug | string | Yes | The place slug, e.g. "ongtong-khaosoi-ari-branch-8cszby" |
Parameters from the server's own tool schema.
Why get_place is rated Low
This tool retrieves existing business directory data by identifier. It has no side effects, cannot modify data, execute code, or incur financial obligations. The blast radius of misuse is minimal (e.g., exposing business contact details, but no destructive outcome). Classification: Read with low severity.
From the tool's definition Tool description states 'Get the full structured record for one place' — a retrieval operation with no modification, deletion, or execution capability. The slug-based lookup is a simple data fetch.
Attacks that exploit this kind of access
The rule that runs get_place 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_place, this is the rule to start with:
get_place 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_place call is checked against it from then on.
Questions about get_place
Get the full structured record for one place — any of the 14 Southeast Asian cities — by its Booyah Index slug (from search_places results). It is categorised as a Read tool in the Booyah Index MCP Server, which means it retrieves data without modifying state.
get_place accepts 1 parameter: slug. Required: slug. 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_place: 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_place 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_place 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_place. 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_place 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