companion_cron_list
List the armed crons for a companion project with their schedules and last outcomes.
This record as markdown: /tools/io-github-kivanccakmak-yaver/companion-cron-list.md
What companion_cron_list does on Yaver
AI agents call companion_cron_list 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
project | string | Yes | Companion project slug |
Parameters from the server's own tool schema.
Why companion_cron_list is rated Low
This tool performs a read-only query to retrieve cron job metadata (schedules and last outcomes) for informational purposes. There is no creation, modification, deletion, or execution of cron jobs—only introspection of their state. The blast radius if misused is minimal, as an attacker learns only about existing scheduled tasks, not their actual execution or control.
From the tool's definition Tool name and description indicate a list operation: 'List the armed crons for a companion project with their schedules and last outcomes.' The verb 'list' retrieves information about existing cron jobs without modifying, deleting, or executing them.
Attacks that exploit this kind of access
The rule that runs companion_cron_list 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 companion_cron_list, this is the rule to start with:
companion_cron_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 Yaver, apply this rule, and every companion_cron_list call is checked against it from then on.
Questions about companion_cron_list
List the armed crons for a companion project with their schedules and last outcomes. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
companion_cron_list accepts 1 parameter: project. Required: project. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for companion_cron_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 Yaver. Nothing to install.
companion_cron_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 companion_cron_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 companion_cron_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.
companion_cron_list 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.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue