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.
This record as markdown: /tools/404-team-not-found/optimise-berth-cranes.md
What optimise_berth_cranes does on 404-Team-Not-Found
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.
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.
Attacks that exploit this kind of access
The rule that runs optimise_berth_cranes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 404-Team-Not-Found, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For optimise_berth_cranes, this is the rule to start with:
optimise_berth_cranes stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 404-Team-Not-Found, apply this rule, and every optimise_berth_cranes call is checked against it from then on.
Questions about 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. It is categorised as a Execute tool in the 404-Team-Not-Found MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the 404-Team-Not-Found MCP server in PolicyLayer and add a rule for optimise_berth_cranes: 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 404-Team-Not-Found. Nothing to install.
optimise_berth_cranes is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the optimise_berth_cranes 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 optimise_berth_cranes. 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.
optimise_berth_cranes is provided by the 404-Team-Not-Found MCP server (Aryan-B-Parikh/404-Team-Not-Found). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 404-Team-Not-Found, and thousands of servers like it.
Across the catalogue