morning_latest · Yaver MCP: Risk & Policy

WHAT IT DOES

What morning_latest does on Yaver

AI agents invoke morning_latest to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why morning_latest needs a policy

morning_latest triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

morning_latest Rate-limited

morning_latest stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "morning_latest": {
      "limits": [
        {
          "counter": "morning_latest_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Yaver, so you can run agents against it safely.

FAQ

Questions about morning_latest

What does the morning_latest tool do? +

Return the most recent morning match-report — what shipped overnight from an autodev run. One line per task: title, status (shipped/failed/rolled-back), files changed, commit sha, whether a video was captured. Use when the user asks what ran overnight or what's new. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on morning_latest? +

Register the Yaver MCP server in PolicyLayer and add a rule for morning_latest: 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 morning_latest? +

morning_latest is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit morning_latest? +

Yes. Add a rate_limit block to the morning_latest 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 morning_latest completely? +

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

morning_latest 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.