find_tasks_by_file
Find which tasks are linked to a specific file path. Shows who
This record as markdown: /tools/todos/find-tasks-by-file.md
What find_tasks_by_file does on Todos
AI agents call find_tasks_by_file 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 find_tasks_by_file is rated Low
This tool retrieves or queries data about task-file associations with no side effects. It does not create, modify, delete, or execute any operations—it only returns information about existing relationships between tasks and files. This is a classic Read operation with minimal security risk.
From the tool's definition The tool 'find_tasks_by_file' performs a query operation to retrieve tasks linked to a specific file path. The description indicates it 'shows' results without modifying or deleting data.
Attacks that exploit this kind of access
The rule that runs find_tasks_by_file 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 find_tasks_by_file, this is the rule to start with:
find_tasks_by_file 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 find_tasks_by_file call is checked against it from then on.
Questions about find_tasks_by_file
Find which tasks are linked to a specific file path. Shows who. 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 find_tasks_by_file: 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.
find_tasks_by_file 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 find_tasks_by_file 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 find_tasks_by_file. 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.
find_tasks_by_file 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