# 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).

Agent View of the PolicyLayer registry record for `get_place`. HTML page: https://policylayer.com/tools/com-getbooyah-booyah-index/get-place

## Facts

- Tool: `get_place`
- Server: Booyah Index (`https://getbooyah.com/api/mcp`) — https://policylayer.com/tools/com-getbooyah-booyah-index.md
- Homepage: https://github.com/https://getbooyah.com/api/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| 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.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_place",
    "arguments": {
      "slug": "<slug>"
    }
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Booyah Index:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_place": {}
  }
}
```

## Other tools on Booyah Index (5)

- `get_product` — Read — https://policylayer.com/tools/com-getbooyah-booyah-index/get-product.md
- `get_store` — Read — https://policylayer.com/tools/com-getbooyah-booyah-index/get-store.md
- `list_cities` — Read — https://policylayer.com/tools/com-getbooyah-booyah-index/list-cities.md
- `search_places` — Read — https://policylayer.com/tools/com-getbooyah-booyah-index/search-places.md
- `search_products` — Read — https://policylayer.com/tools/com-getbooyah-booyah-index/search-products.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-getbooyah-booyah-index · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-getbooyah-booyah-index