newsletter_compose_from_git · Yaver MCP: Risk & Policy

WHAT IT DOES

What newsletter_compose_from_git does on Yaver

AI agents use newsletter_compose_from_git to create or update resources in Yaver — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.

PARAMETERS

Parameter	Type	Required	Description
`repo`	string	Yes	Absolute repo path
`execute`	boolean	—	Pipe through runner for polish
`subject`	string	—
`saveDraft`	boolean	—
`sinceDays`	integer	—	Default 7
`includePrs`	boolean	—
`instructions`	string	—	Tone notes for the AI polish pass
`includeIssues`	boolean	—

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why newsletter_compose_from_git needs a policy

An AI agent can call newsletter_compose_from_git faster than any human can review — one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

newsletter_compose_from_git Rate-limited

newsletter_compose_from_git stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "newsletter_compose_from_git": {
      "limits": [
        {
          "counter": "newsletter_compose_from_git_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 newsletter_compose_from_git

What does the newsletter_compose_from_git tool do? +

Walk git log + gh/glab PRs and issues for a repo + window and draft a weekly recap newsletter. Optionally pipe through the AI runner for tone polish, and optionally save as a campaign draft. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does newsletter_compose_from_git accept? +

newsletter_compose_from_git accepts 8 parameters: repo, execute, subject, saveDraft, sinceDays, includePrs, instructions, includeIssues. Required: repo. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on newsletter_compose_from_git? +

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

newsletter_compose_from_git is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit newsletter_compose_from_git? +

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

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

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