Return the current task list from todo.json. Each task has an energy_required
AI agents call get_tasks to retrieve information from Wellness Planner 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 existing task data from a local JSON file without creating, modifying, or deleting any information. It is a straightforward read operation that presents no risk of data loss, code execution, financial impact, or destructive action. The low severity reflects minimal blast radius from misuse—an AI agent can only view task information, which poses negligible security concern.
From the tool's definition Tool name 'get_tasks' and description 'Return the current task list from todo.json' indicate a retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
Return the current task list from todo.json. Each task has an energy_required. It is categorised as a Read tool in the Wellness Planner MCP Server, which means it retrieves data without modifying state.
Register the Wellness Planner MCP server in PolicyLayer and add a rule for get_tasks: 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 Wellness Planner. Nothing to install.
get_tasks 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_tasks 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_tasks. 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_tasks is provided by the Wellness Planner MCP server (rwking/wellness_planner). 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 →