check_file_lock

Check who holds a lock on a file path. Returns null if unlocked or expired.

Server Todos @hasna/todos
Category Read
Risk class Low
Parameters 00 required

What check_file_lock does on Todos

AI agents call check_file_lock to retrieve information from Todos without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why check_file_lock needs a policy

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.

Questions about check_file_lock

What does the check_file_lock tool do? +

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.

How do I enforce a policy on check_file_lock? +

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.

What risk level is check_file_lock? +

check_file_lock is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_file_lock? +

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.

How do I block check_file_lock completely? +

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.

What MCP server provides check_file_lock? +

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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.