Conversation
Contributor
posthog-python Compliance ReportDate: 2026-10-02T08:21:15.767961+00:00 ✅ All Tests Passed!121/121 tests passed Capture_V1 Tests✅ 95/95 tests passed View Details
Capture_Ai Tests✅ 5/5 tests passed View Details
Feature_Flags Tests✅ 17/17 tests passed View Details
Feature_Flags_Local_Evaluation Tests✅ 4/4 tests passed View Details
|
Contributor
|
[Medium risk] Adds safe input field name recording to MCP tool-call events. The PR should not merge until declared input names are captured for referenced standalone FastMCP schemas. Reviews (2) · Last reviewed commit: "fix(mcp): scope input schemas to tool ca..." |
gesh
force-pushed
the
posthog/mcp-input-names
branch
from
October 1, 2026 14:55
2f602c9 to
57a3d9a
Compare
gesh
marked this pull request as ready for review
October 1, 2026 15:07
Generated-By: PostHog Desktop Task-Id: dda38523-5b8d-47b6-a11a-64cd59a812fe
Generated-By: PostHog Desktop Task-Id: dda38523-5b8d-47b6-a11a-64cd59a812fe
gesh
force-pushed
the
posthog/mcp-input-names
branch
from
October 1, 2026 16:02
c8b2409 to
c520c54
Compare
lucasheriques
approved these changes
Oct 1, 2026
lucasheriques
left a comment
Contributor
There was a problem hiding this comment.
The no-values design and the analytics-key filtering hold up. Approving, with a few parity questions, since the same property would carry different data in Python and JS.
Generated-By: PostHog Desktop Task-Id: dda38523-5b8d-47b6-a11a-64cd59a812fe
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
💡 Motivation and Context
MCP server owners need to measure which input names agents use. This must not expose argument values or unknown field names.
This PR ports the input-name and alias contract from
@posthog/mcp0.19.0 and 0.20.0. It adds$mcp_input_keys,$mcp_input_aliases_used, and a helper for custom dispatchers.💚 How did you test it?
uv run pytest -q posthog/test/mcp --timeout=30uv run ruff check posthog/mcp posthog/test/mcp/test_tool_input.py posthog/test/mcp/test_features_m4.pyuv run mypy --no-site-packages --config-file mypy.ini posthog/mcp | uv run mypy-baseline filtermake public_api_check📝 Checklist
If releasing new changes
sampo addto generate a changeset file🤖 Agent context
Autonomy: Human-driven (agent-assisted)
Codex implemented the agreed Python port. The implementation keeps schemas isolated by session and redacts unknown names by default.
Created with PostHog Desktop