get_health
Get system health: task counts by status, active agents, project summary.
This record as markdown: /tools/todos/get-health.md
What get_health does on Todos
AI agents call get_health 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 get_health is rated Low
This tool only retrieves and queries system health information. It has no side effects, does not modify data, execute commands, or trigger external operations. The blast radius of misuse is minimal—an agent with this tool can only read monitoring data about the task management system's current state.
From the tool's definition Tool name is 'get_health' and description states it retrieves 'task counts by status, active agents, project summary' — pure read operations with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs get_health 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 get_health, this is the rule to start with:
get_health 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 get_health call is checked against it from then on.
Questions about get_health
Get system health: task counts by status, active agents, project summary. 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 get_health: 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.
get_health 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_health 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_health. 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_health 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