# optimise_berth_cranes

Run the real OR-Tools CP-SAT berth allocation and quay-crane assignment under physical constraints and compare it with FIFO. Use crane_factor and move_rate_per_crane_hour for capacity/productivity what-if analysis.

Agent View of the PolicyLayer registry record for `optimise_berth_cranes`. HTML page: https://policylayer.com/tools/404-team-not-found/optimise-berth-cranes

## Facts

- Tool: `optimise_berth_cranes`
- 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: Execute (High risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "optimise_berth_cranes",
    "arguments": {}
  }
}
```

## Why optimise_berth_cranes is rated High

optimise_berth_cranes triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

## Use case

AI agents invoke optimise_berth_cranes to trigger actions in 404-Team-Not-Found. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. 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": {
    "optimise_berth_cranes": {
      "limits": [
        {
          "counter": "optimise_berth_cranes_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

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

- `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
- `recommend_routing` — Read — https://policylayer.com/tools/404-team-not-found/recommend-routing.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