lock_user · Tonle OpenProject MCP Server MCP: Risk & Policy

WHAT IT DOES

What lock_user does on Tonle OpenProject MCP Server

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

WHY IT NEEDS A POLICY

Why lock_user needs a policy

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

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lock_user Rate-limited

lock_user 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": {
    "lock_user": {
      "limits": [
        {
          "counter": "lock_user_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 Tonle OpenProject MCP Server, so you can run agents against it safely.

FAQ

Questions about lock_user

What does the lock_user tool do? +

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

How do I enforce a policy on lock_user? +

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

What risk level is lock_user? +

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

Can I rate-limit lock_user? +

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

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

lock_user is provided by the Tonle OpenProject MCP Server MCP server (liratanak/openproject-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

lock_user is one line of Tonle OpenProject MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →