# recommend_routing

Recommend vessel actions: DIVERT, SLOW_STEAM, PRIORITY_WINDOW or HOLD. Returns predicted wait, sustained-congestion evidence, estimated savings, confidence and rationale.

Agent View of the PolicyLayer registry record for `recommend_routing`. HTML page: https://policylayer.com/tools/404-team-not-found/recommend-routing

## Facts

- Tool: `recommend_routing`
- Server: 404-Team-Not-Found (`Aryan-B-Parikh/404-Team-Not-Found`) — https://policylayer.com/tools/404-team-not-found.md
- Homepage: https://github.com/Aryan-B-Parikh/404-Team-Not-Found
- Risk category: Read (Low risk)
- Registry record: grade D, 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": "recommend_routing",
    "arguments": {}
  }
}
```

## Why recommend_routing is rated Low

Even though recommend_routing only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call recommend_routing to retrieve information from 404-Team-Not-Found 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 404-Team-Not-Found:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "recommend_routing": {}
  }
}
```

## Other tools on 404-Team-Not-Found (11)

- `optimise_berth_cranes` — Execute — https://policylayer.com/tools/404-team-not-found/optimise-berth-cranes.md
- `simulate_scenario` — Execute — https://policylayer.com/tools/404-team-not-found/simulate-scenario.md
- `ask_operations_question` — Read — https://policylayer.com/tools/404-team-not-found/ask-operations-question.md
- `detect_anomalies` — Read — https://policylayer.com/tools/404-team-not-found/detect-anomalies.md
- `forecast_congestion` — Read — https://policylayer.com/tools/404-team-not-found/forecast-congestion.md
- `get_data_provenance` — Read — https://policylayer.com/tools/404-team-not-found/get-data-provenance.md
- `get_port_overview` — Read — https://policylayer.com/tools/404-team-not-found/get-port-overview.md
- `get_terminals` — Read — https://policylayer.com/tools/404-team-not-found/get-terminals.md
- `query_vessels` — Read — https://policylayer.com/tools/404-team-not-found/query-vessels.md
- `rank_hotspots` — Read — https://policylayer.com/tools/404-team-not-found/rank-hotspots.md
- `generate_operations_plan` — Write — https://policylayer.com/tools/404-team-not-found/generate-operations-plan.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=404-team-not-found · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/404-team-not-found