score-venues
Score candidate venues by travel time fairness for multiple participants.
This record as markdown: /tools/dev-forgesworn-rendezvous-mcp/score-venues.md
What score-venues does on Rendezvous
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.
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 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.
Attacks that exploit this kind of access
The rule that runs score-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 score-venues, this is the rule to start with:
score-venues 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 Rendezvous, apply this rule, and every score-venues call is checked against it from then on.
Questions about score-venues
Score candidate venues by travel time fairness for multiple participants. It is categorised as a Read tool in the Rendezvous MCP Server, which means it retrieves data without modifying state.
Register the Rendezvous MCP server in PolicyLayer and add a rule for score-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.
score-venues 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 score-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.
Set action: deny in the PolicyLayer policy for score-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.
score-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.
More on Rendezvous, and thousands of servers like it.
This server
Across the catalogue