get_project_tasks_by_name
Get all pending tasks for a project by project name, sorted by creation time
This record as markdown: /tools/todo-for-ai-todo-for-ai-mcp/get-project-tasks-by-name.md
What get_project_tasks_by_name does on Todo for AI MCP Server
AI agents call get_project_tasks_by_name to retrieve information from Todo for AI MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_project_tasks_by_name is rated Low
This tool only retrieves and queries task data from a project without any ability to modify, delete, or execute operations. It has minimal security risk as it simply returns filtered task information. The severity is low because even misuse would only expose existing task data rather than causing damage or side effects.
From the tool's definition Tool name contains 'get' and description states 'Get all pending tasks for a project' - a retrieval operation with no modification capability. The description specifies it returns existing data sorted by creation time.
Attacks that exploit this kind of access
The rule that runs get_project_tasks_by_name safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Todo for AI MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_project_tasks_by_name, this is the rule to start with:
get_project_tasks_by_name 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 Todo for AI MCP Server, apply this rule, and every get_project_tasks_by_name call is checked against it from then on.
Questions about get_project_tasks_by_name
Get all pending tasks for a project by project name, sorted by creation time. It is categorised as a Read tool in the Todo for AI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Todo for AI MCP Server MCP server in PolicyLayer and add a rule for get_project_tasks_by_name: 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 Todo for AI MCP Server. Nothing to install.
get_project_tasks_by_name 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 get_project_tasks_by_name 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 get_project_tasks_by_name. 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.
get_project_tasks_by_name is provided by the Todo for AI MCP Server MCP server (todo-for-ai/todo-for-ai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Todo for AI MCP Server, and thousands of servers like it.
This server
Across the catalogue