propose_next_best_move · Livepilot MCP: Risk & Policy

WHAT IT DOES

What propose_next_best_move does on Livepilot

AI agents use propose_next_best_move to create or update resources in Livepilot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Livepilot environment.

WHY IT NEEDS A POLICY

Why propose_next_best_move needs a policy

An AI agent can call propose_next_best_move faster than any human can review — one bad instruction and it creates or modifies resources in Livepilot by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

propose_next_best_move Rate-limited

propose_next_best_move stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "propose_next_best_move": {
      "limits": [
        {
          "counter": "propose_next_best_move_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Livepilot, so you can run agents against it safely.

FAQ

Questions about propose_next_best_move

What does the propose_next_best_move tool do? +

propose_next_best_move. It is categorised as a Write tool in the Livepilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on propose_next_best_move? +

Register the Livepilot MCP server in PolicyLayer and add a rule for propose_next_best_move: 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 Livepilot. Nothing to install.

What risk level is propose_next_best_move? +

propose_next_best_move is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit propose_next_best_move? +

Yes. Add a rate_limit block to the propose_next_best_move 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.

How do I block propose_next_best_move completely? +

Set action: deny in the PolicyLayer policy for propose_next_best_move. 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.

What MCP server provides propose_next_best_move? +

propose_next_best_move is provided by the Livepilot MCP server (livepilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.