Return every stored task with its Markdown summary and raw detail payload. Use this right after creating/updating schedules or whenever the user wants a dashboard view. If the user says “show my paused jobs”, call this with status=
AI agents call list_tasks to retrieve information from Schedule Task MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays stored task data without creating, modifying, deleting, or executing any tasks. It has no side effects beyond querying the SQLite database. Even though the server manages scheduled task execution (which could be Execute category), this specific tool is limited to listing/querying existing tasks.
From the tool's definition Tool name is 'list_tasks' and description states it will 'Return every stored task' with summaries and payloads. The verb 'return' and 'show' indicate data retrieval with no modification.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Return every stored task with its Markdown summary and raw detail payload. Use this right after creating/updating schedules or whenever the user wants a dashboard view. If the user says “show my paused jobs”, call this with status=. It is categorised as a Read tool in the Schedule Task MCP MCP Server, which means it retrieves data without modifying state.
Register the Schedule Task MCP server in PolicyLayer and add a rule for list_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 Schedule Task MCP. Nothing to install.
list_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 list_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 list_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.
list_tasks is provided by the Schedule Task MCP server (liao1fan/schedule-task-mcp). 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 →