list_schedules

List all scheduled and recurring tasks with their status, next run time, and history.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/list-schedules.md

WHAT IT DOES

What list_schedules does on Yaver

AI agents call list_schedules to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_schedules is rated Low

This tool retrieves information about scheduled tasks (status, timing, history) without creating, modifying, executing, or deleting anything. It is a read-only query operation with minimal security impact—knowing what tasks are scheduled poses no direct risk compared to actually running them.

From the tool's definition Tool name 'list_schedules' and description 'List all scheduled and recurring tasks with their status, next run time, and history' indicate retrieval/querying of existing task metadata with no modification, deletion, or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_schedules safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_schedules, this is the rule to start with:

list_schedules Allowed

list_schedules is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_schedules": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every list_schedules call is checked against it from then on.

FAQ

Questions about list_schedules

What does the list_schedules tool do? +

List all scheduled and recurring tasks with their status, next run time, and history. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_schedules? +

Register the Yaver MCP server in PolicyLayer and add a rule for list_schedules: 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 Yaver. Nothing to install.

What risk level is list_schedules? +

list_schedules is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_schedules? +

Yes. Add a rate_limit block to the list_schedules 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.

How do I block list_schedules completely? +

Set action: deny in the PolicyLayer policy for list_schedules. 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.

What MCP server provides list_schedules? +

list_schedules is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →