Skip to content

feat(mcp): observability audit export tools (#77) - #88

Merged
jusso-dev merged 1 commit into
mainfrom
agent/mcp-observability-77
Jul 28, 2026
Merged

feat(mcp): observability audit export tools (#77)#88
jusso-dev merged 1 commit into
mainfrom
agent/mcp-observability-77

Conversation

@jusso-dev

Copy link
Copy Markdown
Owner

Summary

Closes #77 / tracker #78 item 6.

  • muster_list_invocations — recent mcp.tool.invoked audit rows (needs audit.read)
  • muster_export_audit — bounded export of MCP/integration/knowledge audit actions (needs audit.export)
  • Metadata allow-list only (hashes, outcomes, tool versions) — no CoT / prompts
  • Explicit replay.mayRepeatExternalActions: false

Test plan

  • unit tests + tsc on @muster/mcp

Add MCP observability tools that read organisation-scoped audit records
with redacted metadata only — no private reasoning, no external replay.
@jusso-dev
jusso-dev merged commit 740bab9 into main Jul 28, 2026
@jusso-dev
jusso-dev deleted the agent/mcp-observability-77 branch July 28, 2026 07:15
@coderabbitai

coderabbitai Bot commented Jul 28, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@jusso-dev, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 1 minute

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: c6e87947-3d86-4873-a365-f3418acd2a6b

📥 Commits

Reviewing files that changed from the base of the PR and between 0e624ae and 99db495.

📒 Files selected for processing (7)
  • packages/mcp/src/actions.test.ts
  • packages/mcp/src/constants.ts
  • packages/mcp/src/index.ts
  • packages/mcp/src/mcp.integration.test.ts
  • packages/mcp/src/observability.ts
  • packages/mcp/src/server.ts
  • skills/policy-bundle.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch agent/mcp-observability-77

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Audit and evaluate governed Muster operations without private reasoning

1 participant