AI agents call get_todos_tool to retrieve information from Alaya without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves task data from the vault without creating, modifying, deleting, or executing any operations. It is a straightforward search/read function that returns information about existing todos, with optional filtering by directory. No side effects occur. The low severity reflects minimal blast radius — listing todos poses no risk of data loss, financial impact, or unintended execution.
From the tool's definition Tool description states 'Find all open tasks' — a retrieval operation with no modification or execution. The syntax '- [ ]' indicates reading task metadata from existing notes.
Attacks that exploit this kind of access
Find all open tasks (- [ ] ...) in the vault. Optionally restrict to directories. It is categorised as a Read tool in the Alaya MCP Server, which means it retrieves data without modifying state.
Register the Alaya MCP server in PolicyLayer and add a rule for get_todos_tool: 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 Alaya. Nothing to install.
get_todos_tool 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_todos_tool 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_todos_tool. 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_todos_tool is provided by the Alaya MCP server (luke-kucing/alaya). 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 →