project_status_set · Lockstep MCP: Risk & Policy

WHAT IT DOES

What project_status_set does on Lockstep

AI agents use project_status_set 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 project_status_set needs a policy

This tool writes/updates a project status field, which is a reversible data modification. Misuse could mislead coordinating agents about project state, causing coordination failures, but it does not delete data, execute code, or involve finances.

From the tool's definition 'Set the project status' — the tool modifies project state data

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

project_status_set Rate-limited

project_status_set 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": {
    "project_status_set": {
      "limits": [
        {
          "counter": "project_status_set_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 project_status_set

What does the project_status_set tool do? +

Set the project status. Use. 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 project_status_set? +

Register the Lockstep MCP server in PolicyLayer and add a rule for project_status_set: 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 project_status_set? +

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

Can I rate-limit project_status_set? +

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

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

project_status_set 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.