AI agents call system_scheduled_tasks to retrieve information from Infra Ops without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about scheduled tasks without side effects. The underlying commands are all read-only queries that enumerate existing schedules. While scheduled tasks can be sensitive (revealing automation and system operations), the tool itself only reads and lists them, making it a Read category risk.
From the tool's definition Tool performs listing operations: 'List scheduled tasks' using read-only commands (schtasks on Windows, crontab -l on Linux, launchctl list on macOS). These commands query and display scheduled tasks without modification or execution.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
List scheduled tasks. Uses schtasks on Windows, crontab -l on Linux, launchctl list on macOS. It is categorised as a Read tool in the Infra Ops MCP Server, which means it retrieves data without modifying state.
Register the Infra Ops MCP server in PolicyLayer and add a rule for system_scheduled_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 Infra Ops. Nothing to install.
system_scheduled_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 system_scheduled_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 system_scheduled_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.
system_scheduled_tasks is provided by the Infra Ops MCP server (skyvanguard/infra-ops-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 →