This record as markdown: /tools/mukul975-mcp-windows-automation/task-scheduler-list.md
What task_scheduler_list does on Mcp Windows
AI agents call task_scheduler_list to retrieve information from Mcp Windows without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why task_scheduler_list is rated Low
This tool retrieves information about scheduled tasks on a Windows system without modifying, executing, or deleting anything. It is a passive read operation that provides visibility into existing system state. The low severity reflects minimal blast radius—an AI agent misusing this tool could only enumerate scheduled tasks, which does not directly harm the system or data.
From the tool's definition Tool name 'task_scheduler_list' and description 'List scheduled tasks' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs task_scheduler_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Windows, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For task_scheduler_list, this is the rule to start with:
task_scheduler_list 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 Mcp Windows, apply this rule, and every task_scheduler_list call is checked against it from then on.
Questions about task_scheduler_list
List scheduled tasks. It is categorised as a Read tool in the Mcp Windows MCP Server, which means it retrieves data without modifying state.
Register the Mcp Windows MCP server in PolicyLayer and add a rule for task_scheduler_list: 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 Mcp Windows. Nothing to install.
task_scheduler_list 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 task_scheduler_list 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 task_scheduler_list. 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.
task_scheduler_list is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Windows, and thousands of servers like it.
This server
Across the catalogue