Club moorage within a radius of a position, nearest first — RVYC outstations
AI agents call find_moorage_near to retrieve information from Outstations without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and searches existing moorage records from a preloaded database of Royal Victoria Yacht Club outstations. It performs a geospatial query with no side effects, matching the 'Read' category. The blast radius of misuse is minimal—returning irrelevant or all records causes no harm to data, systems, or financial state.
From the tool's definition Tool name 'find_moorage_near' and description 'Club moorage within a radius of a position, nearest first' indicate a query/search operation that retrieves moorage information based on geographic proximity.
Attacks that exploit this kind of access
Club moorage within a radius of a position, nearest first — RVYC outstations. It is categorised as a Read tool in the Outstations MCP Server, which means it retrieves data without modifying state.
Register the Outstations MCP server in PolicyLayer and add a rule for find_moorage_near: 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 Outstations. Nothing to install.
find_moorage_near 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 find_moorage_near 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 find_moorage_near. 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.
find_moorage_near is provided by the Outstations MCP server (sailingnaturali/outstations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →