# score-venues

Score candidate venues by travel time fairness for multiple participants.

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

## Facts

- Tool: `score-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": "score-venues",
    "arguments": {}
  }
}
```

## Why score-venues is rated Low

This tool performs a read-only analytical operation on venue and travel time data to compute fairness scores. It retrieves or processes existing information without creating side effects, modifying state, deleting data, executing arbitrary code, or committing financial obligations. The most severe category applicable is Read.

From the tool's own definition: "The tool 'score-venues' analyzes and scores venues based on travel time fairness metrics. The verb 'score' indicates evaluation/computation of existing data rather than creation, modification, deletion, or execution of external operations."

## Use case

AI agents call score-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": {
    "score-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
- `search-venues` — Read — https://policylayer.com/tools/dev-forgesworn-rendezvous-mcp/search-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