check_file_lock
Check who holds a lock on a file path. Returns null if unlocked or expired.
This record as markdown: /tools/todos/check-file-lock.md
What check_file_lock does on Todos
AI agents call check_file_lock to retrieve information from Todos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_file_lock is rated Low
This tool only queries the state of file locks and returns information; it does not create, modify, delete, execute operations, or cause any irreversible changes. It is a straightforward read operation with minimal risk if misused by an AI agent.
From the tool's definition The tool 'check_file_lock' is described as checking who holds a lock on a file path and returning null if unlocked or expired. The verb 'check' and the return-only nature indicate pure information retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs check_file_lock safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Todos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_file_lock, this is the rule to start with:
check_file_lock is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Todos, apply this rule, and every check_file_lock call is checked against it from then on.
Questions about check_file_lock
Check who holds a lock on a file path. Returns null if unlocked or expired. It is categorised as a Read tool in the Todos MCP Server, which means it retrieves data without modifying state.
Register the Todos MCP server in PolicyLayer and add a rule for check_file_lock: 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 Todos. Nothing to install.
check_file_lock is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_file_lock 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 check_file_lock. 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.
check_file_lock is provided by the Todos MCP server (@hasna/todos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Todos, and thousands of servers like it.
This server
Across the catalogue