lock_files · Coord MCP: Risk & Policy

WHAT IT DOES

What lock_files does on CoordMCP

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

WHY IT NEEDS A POLICY

Why lock_files needs a policy

File locking is a write operation that modifies coordination metadata. While the description is empty, context from sibling tools and the server's purpose (preventing conflicts via file locking in multi-agent coordination) indicates this tool creates or updates lock state.

From the tool's definition Tool name 'lock_files' indicates it acquires or modifies file lock state. Sibling tools like 'create_project', 'create_task', and 'complete_task' establish this as a coordination/state-management server.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lock_files Rate-limited

lock_files 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_files": {
      "limits": [
        {
          "counter": "lock_files_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 CoordMCP, so you can run agents against it safely.

FAQ

Questions about lock_files

What does the lock_files tool do? +

lock_files. It is categorised as a Write tool in the CoordMCP 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_files? +

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

What risk level is lock_files? +

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

Can I rate-limit lock_files? +

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

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

lock_files is provided by the Coord MCP server (siddiquesahabaj/coordmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.