AI agents use unlock_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.
Unlocking files is a reversible write operation that modifies lock metadata rather than file content. It could enable unintended concurrent modifications if misused by an AI agent, but the effect is recoverable by re-locking. The empty description lowers confidence slightly, but the name and context clearly indicate this is a locking mechanism tool.
From the tool's definition Tool name 'unlock_files' indicates modification of file lock state; server description mentions 'file locking' as a core feature for preventing conflicts across agents.
Attacks that exploit this kind of access
unlock_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.
Register the Coord MCP server in PolicyLayer and add a rule for unlock_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.
unlock_files is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the unlock_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.
Set action: deny in the PolicyLayer policy for unlock_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.
unlock_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →