Dark Mode

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

feat: add mcpCheckInput and mcpCheckOutput methods#101

Merged
saurabhjain1592 merged 7 commits intomainfrom
feat/mcp-check-endpoints
Feb 28, 2026
Merged

feat: add mcpCheckInput and mcpCheckOutput methods#101
saurabhjain1592 merged 7 commits intomainfrom
feat/mcp-check-endpoints

Conversation

Copy link
Member

saurabhjain1592 commented Feb 27, 2026

Summary

  • Add mcpCheckInput and mcpCheckOutput methods (sync + async CompletableFuture variants)
  • Add MCPCheckInputRequest, MCPCheckInputResponse, MCPCheckOutputRequest, MCPCheckOutputResponse POJOs
  • 403 responses treated as valid policy-blocked results, not errors

Context

Standalone policy-check endpoints (getaxonflow/axonflow-enterprise#1258) allow external orchestrators to use AxonFlow as a policy gate.

Test plan

  • mvn compile passes
  • CI passes

saurabhjain1592 added 7 commits February 27, 2026 19:06
Add standalone policy-check methods and request/response POJOs for external
orchestrators to use AxonFlow as a policy gate. Includes sync and async
(CompletableFuture) variants. 403 responses are treated as valid
policy-blocked results, not errors.

Refs: getaxonflow/axonflow-enterprise#1258
Cover mcpCheckInput and mcpCheckOutput SDK methods and their
associated request/response types to restore JaCoCo coverage
above the 73% threshold.

Tests added:
- mcpCheckInput: basic call, with options, 403 blocked result,
500 error, null validation, async variant
- mcpCheckOutput: basic call, with options, 403 blocked result,
exfiltration info, 500 error, null validation, async variant
- MCPCheckInputRequest: construction, serialization, equals/hashCode
- MCPCheckInputResponse: construction, deserialization, equals/hashCode
- MCPCheckOutputRequest: construction, serialization, equals/hashCode
- MCPCheckOutputResponse: construction, deserialization, equals/hashCode
...ests

The API contract allows check-output requests with message only (no
response_data) for execute-style validation. Removed the
Objects.requireNonNull check on responseData and updated the test to
verify execute-style requests with null responseData work correctly.
saurabhjain1592 merged commit 641638d into main Feb 28, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant