# search-venues

Search for venues (pubs, cafes, restaurants, parks, etc.) near a location using OpenStreetMap data.

Agent View of the PolicyLayer registry record for `search-venues`. HTML page: https://policylayer.com/tools/dev-forgesworn-rendezvous-mcp/search-venues

## Facts

- Tool: `search-venues`
- Server: Rendezvous (`rendezvous-mcp`) — https://policylayer.com/tools/dev-forgesworn-rendezvous-mcp.md
- Install: `npx -y rendezvous-mcp`
- Homepage: https://github.com/forgesworn/rendezvous-mcp
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "search-venues",
    "arguments": {}
  }
}
```

## Why search-venues is rated Low

This tool retrieves venue information from OpenStreetMap without creating, modifying, or deleting data. It is a straightforward read operation that queries a mapping database. The low severity reflects minimal risk if misused by an AI agent—the worst case would be returning irrelevant venue results, which has negligible security impact.

From the tool's own definition: "Tool searches for venues using OpenStreetMap data and returns results. The description explicitly describes a search operation with no modification, deletion, or execution of external systems. No side effects are mentioned."

## Use case

AI agents call search-venues to retrieve information from Rendezvous 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 Rendezvous:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search-venues": {}
  }
}
```

## Other tools on Rendezvous (4)

- `get-directions` — Read — https://policylayer.com/tools/dev-forgesworn-rendezvous-mcp/get-directions.md
- `get-isochrone` — Read — https://policylayer.com/tools/dev-forgesworn-rendezvous-mcp/get-isochrone.md
- `score-venues` — Read — https://policylayer.com/tools/dev-forgesworn-rendezvous-mcp/score-venues.md
- `store-routing-credentials` — Write — https://policylayer.com/tools/dev-forgesworn-rendezvous-mcp/store-routing-credentials.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=dev-forgesworn-rendezvous-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-forgesworn-rendezvous-mcp