coordination_init · Lockstep MCP: Risk & Policy

WHAT IT DOES

What coordination_init does on Lockstep

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

WHY IT NEEDS A POLICY

Why coordination_init needs a policy

This tool initializes a coordination session, which involves creating/writing session state and role assignments. It's not purely read-only since it 'sets up' a role and project state. It's not destructive or financial. The blast radius is medium since misuse could disrupt multi-agent coordination sessions, but data loss is unlikely.

From the tool's definition Initialize coordination session... set up your role (planner or implementer)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

coordination_init Rate-limited

coordination_init 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": {
    "coordination_init": {
      "limits": [
        {
          "counter": "coordination_init_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 Lockstep, so you can run agents against it safely.

FAQ

Questions about coordination_init

What does the coordination_init tool do? +

Initialize coordination session. Call this first to set up your role (planner or implementer). Returns guidance based on your role and current project state. It is categorised as a Write tool in the Lockstep MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on coordination_init? +

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

What risk level is coordination_init? +

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

Can I rate-limit coordination_init? +

Yes. Add a rate_limit block to the coordination_init 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 coordination_init completely? +

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

coordination_init is provided by the Lockstep MCP server (tmmoore286/lockstep-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.