[hpouillot]

Problem

MCP users can set issue severity manually, but they cannot create or update automatic severity rules.

Changes

• MCP users can now list, create, and update Error tracking severity rules.
• Tool guidance explains first-match ordering, accepted severities, and new-issue-only behavior.
• Generated handlers, metadata, schemas, and snapshots keep the MCP catalog in sync.

How did you test this code?

• Ran the MCP type checker, formatter, linter, and tool-name validator.
• Ran the tool generation, schema snapshot, catalog, filtering, and search unit tests.
• Added integration coverage for create, update, and list behavior. The integration environment was not configured, so this test did not run locally.

👉 Stay up-to-date with PostHog coding conventions for a smoother review.

Automatic notifications

• Publish to changelog?

Docs update

The generated tool descriptions document the supported inputs and severity-rule behavior. No separate product docs changed.

🤖 Agent context

Autonomy: Human-driven (agent-assisted)

OpenAI GPT-5.6 Sol used pi, GitHub CLI, and PostHog MCP tooling. The work invoked /implementing-mcp-tools, /writing-user-facing-copy, /writing-tests, /writing-code-comments, and /writing-pr-descriptions.

The change also exposes list access so agents can inspect ordered rules before creating or updating one. Delete and reorder operations remain outside this scope.

[trunk-io]

😎 Merged successfully - details.

[github-actions]

Hey @hpouillot! 👋

It looks like your git author email on this PR isn't your @posthog.com address (hpouillot@gmail.com). Since you're on the PostHog team, it's worth pointing your local git author email at your @posthog.com address. Why it matters:

• Consistent work identity in git history — internal tooling that attributes commits to team members keys off your @posthog.com address.
• Keeps team contributions easy to tell apart from external community ones when scanning history.

You can fix it for this repo with:

git config user.email "you@posthog.com"

Or set it globally with git config --global user.email "you@posthog.com". No need to redo this PR — just a nudge for next time. 🙂

[github-actions]

🤖 CI report

⚠️ Trunk lane — backend Python lane

This PR is assigned to the backend Python lane. It runs backend Python tests and may merge in parallel with PRs in other lanes.

ℹ️ MCP UI apps size — 33 app(s), 17662.6 KB JS

Built size of each MCP UI app (main.js + styles.css).

App	JS	CSS
debug	600.0 KB	195.2 KB
action	458.2 KB	195.2 KB
action-list	564.9 KB	195.2 KB
cohort	457.2 KB	195.2 KB
cohort-list	563.8 KB	195.2 KB
email-template	457.0 KB	195.2 KB
error-details	472.9 KB	195.2 KB
error-issue	457.9 KB	195.2 KB
error-issue-list	564.7 KB	195.2 KB
experiment	562.0 KB	195.2 KB
experiment-list	565.6 KB	195.2 KB
experiment-results	567.1 KB	195.2 KB
feature-flag	567.6 KB	195.2 KB
feature-flag-list	571.4 KB	195.2 KB
feature-flag-testing	461.4 KB	195.2 KB
inline-scan	457.7 KB	195.2 KB
insight-actors	563.0 KB	195.2 KB
invite-email-preview	456.4 KB	195.2 KB
llm-costs	560.0 KB	195.2 KB
session-recording	459.0 KB	195.2 KB
survey	458.8 KB	195.2 KB
survey-global-stats	562.7 KB	195.2 KB
survey-list	565.5 KB	195.2 KB
survey-stats	562.7 KB	195.2 KB
trace-span	457.6 KB	195.2 KB
trace-span-list	564.7 KB	195.2 KB
vision-observation-list	563.9 KB	195.2 KB
workflow	457.5 KB	195.2 KB
workflow-list	564.2 KB	195.2 KB
loops-review	461.9 KB	195.2 KB
query-results	755.0 KB	195.2 KB
render-ui	838.1 KB	195.2 KB
visual-review-snapshots	462.0 KB	195.2 KB

[greptile-apps]

_{Reviews (1): Last reviewed commit: "feat(error-tracking): add severity rule ..." | Re-trigger Greptile}

[trunk-io]

   

View Full Report ↗︎ ⋅ Docs

[deployment-status-posthog]

Deploy status

Environment	Status	Deployed At	Workflow
dev	✅ Deployed	2026-08-27 10:28 UTC	Run
prod-us	✅ Deployed	2026-08-27 10:52 UTC	Run
prod-eu	✅ Deployed	2026-08-27 10:53 UTC	Run