search-venues

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

SERVERRendezvous SOURCErendezvous-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade A, identity unverified Pull the record →

This record as markdown: /tools/dev-forgesworn-rendezvous-mcp/search-venues.md

WHAT IT DOES

What search-venues does on Rendezvous

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.

RISK

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search-venues safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Rendezvous, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search-venues, this is the rule to start with:

search-venues Allowed

search-venues is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Rendezvous, apply this rule, and every search-venues call is checked against it from then on.

FAQ

Questions about search-venues

What does the search-venues tool do? +

Search for venues (pubs, cafes, restaurants, parks, etc.) near a location using OpenStreetMap data. It is categorised as a Read tool in the Rendezvous MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search-venues? +

Register the Rendezvous MCP server in PolicyLayer and add a rule for search-venues: 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 Rendezvous. Nothing to install.

What risk level is search-venues? +

search-venues is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search-venues? +

Yes. Add a rate_limit block to the search-venues 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.

How do I block search-venues completely? +

Set action: deny in the PolicyLayer policy for search-venues. 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.

What MCP server provides search-venues? +

search-venues is provided by the Rendezvous MCP server (rendezvous-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Rendezvous, and thousands of servers like it.

This server

All 5 Rendezvous tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →