Example routine

Weekly security audit

Review a codebase and its exposed surface for new security risks every week.

Use this routine

Suggested rhythm

0 9 * * 1

America/Los_Angeles

Expected result

A prioritized security brief with evidence, severity, ownership, and recommended next actions.

What the routine does

Inspect the connected repository and security signals. Prioritize newly introduced or materially changed risks, cite the evidence, and produce a concise remediation plan without making unapproved changes.

Inputs

Repository{{repository}}
The repository or project to inspect.
Example: acme/web-app

Required MCP capabilities

Read repository content
Read security findings

Permission boundary

Connections do not grant blanket access. Discover the MCP tools, enable only the capabilities this responsibility needs, and give write-like actions a separate automatic-execution confirmation.