Conversation
bjoepfeiffer
previously approved these changes
May 5, 2026
Per policy decision, the J1 MCP server will not support destructive operations. Removed the delete-rule tool registration and its description file. Co-authored-by: Cursor <cursoragent@cursor.com>
bjoepfeiffer
approved these changes
May 6, 2026
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.
Summary
Fixes alert rule MCP tool schema gaps that prevented rule updates/renames and adds missing action type support. Addresses TD-8323.
Fixes
versionfield: Added toupdate-inline-question-ruleschema and handler — previously the API rejected all updates with "version not provided"method,endpoint,headersto the action schema — previously stripped on update, silently breaking webhook configsbodytype: Changed fromz.string()toz.union([z.string(), z.record(z.any())])to support object bodiesNew Features
FOR_EACH_ITEMaction: Supportsitems,itemRef, and recursive nestedactionsviaz.lazy()schemaSEND_SLACK_MESSAGEaction: Addedchannelsfield supportCREATE_JIRA_TICKETauto-resolve: AddedautoResolveandresolvedStatusfieldsactionSchemausingz.lazy(), replacing duplicated inline schemas in create and update toolsUPDATE_INLINE_QUESTION_RULEnow returns the full field set (matching the create mutation)Not Included
delete-ruletool: Removed per policy — the J1 MCP server will not support destructive operationsFiles Changed
src/server/mcp-server.ts— Shared action schema, version field supportsrc/types/jupiterone.ts— Addedversion,autoResolve,resolvedStatus,items,itemRef,actionsto typessrc/client/graphql/mutations.ts— Expanded update mutation return fieldssrc/descriptions/create-inline-question-rule.md— FOR_EACH_ITEM and Jira auto-resolve docssrc/descriptions/update-inline-question-rule.md— FOR_EACH_ITEM and Jira auto-resolve docssrc/generated/description-map.ts— RegeneratedTest Plan
All tests executed against the j1dev account using a local MCP server build on branch
TD-8323: