list_items
List items in a todo list via WS todo/item/list.
This record as markdown: /tools/fistacho-ha-nexus-agent/list-items.md
What list_items does on Ha Nexus Agent
AI agents call list_items to retrieve information from Ha Nexus Agent without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_items is rated Low
This tool queries and retrieves todo list items without creating, modifying, deleting, or executing operations. It has no side effects and minimal blast radius even if misused by an AI agent—at worst, it exposes todo list contents the user already has access to.
From the tool's definition Tool name 'list_items' and description 'List items in a todo list' indicate data retrieval with no modification capability. The WebSocket endpoint reference 'todo/item/list' follows a standard read-only list pattern.
Attacks that exploit this kind of access
The rule that runs list_items safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ha Nexus Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_items, this is the rule to start with:
list_items 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 Ha Nexus Agent, apply this rule, and every list_items call is checked against it from then on.
Questions about list_items
List items in a todo list via WS todo/item/list. It is categorised as a Read tool in the Ha Nexus Agent MCP Server, which means it retrieves data without modifying state.
Register the Ha Nexus Agent MCP server in PolicyLayer and add a rule for list_items: 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 Ha Nexus Agent. Nothing to install.
list_items 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 list_items 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 list_items. 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.
list_items is provided by the Ha Nexus Agent MCP server (fistacho/ha-nexus-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ha Nexus Agent, and thousands of servers like it.
This server
Across the catalogue