companion_status
Show a companion project's live state: each cron's schedule, next run, last outcome, and each durable service.
This record as markdown: /tools/io-github-kivanccakmak-yaver/companion-status.md
What companion_status does on Yaver
AI agents call companion_status 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_status is rated Low
This tool retrieves and displays monitoring/status information about a companion project's cron jobs and services. It queries existing state but does not create, modify, delete, or execute operations. The blast radius of misuse is minimal—an attacker could gather information about the project's infrastructure but cannot affect it through this tool.
From the tool's definition Tool name and description: 'Show a companion project's live state: each cron's schedule, next run, last outcome, and each durable service.' The verb 'show' and the focus on querying/displaying state without modifying anything indicates a read-only retrieval…
Attacks that exploit this kind of access
The rule that runs companion_status 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_status, this is the rule to start with:
companion_status 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_status call is checked against it from then on.
Questions about companion_status
Show a companion project's live state: each cron's schedule, next run, last outcome, and each durable service. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
companion_status 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_status: 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_status 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_status 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_status. 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_status 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