reasoning Static interface comparison

Copilot Studio

1.0.2 1.0.4

FAILPending human review

1 new destructive capability requires explicit review.

View the upgrade review as Markdown

A shareable summary of this comparison for an issue, pull request or ticket. Select the text and copy it.

Tools9 → 9
Added0
Removed0
Schema changes1
Input schema changes1
Output schema changes0
Unclassified schema changes0
Description changes2
New write authority0
New destructive authority1
New unknown authority0
AnalysisFAIL

INTERFACE DIFF

What changed, tool by tool

Classification from the recorded findings · definitions from the published snapshots

2 tools with recorded changes

  1. copilot_studio_connectModifiedAuthoritySchemaDescriptionFAILREVIEWINFO

    What changed

    • copilot_studio_connect: declared effect changed from write to destructive.
    • copilot_studio_connect — Schema change: input property added: reauthenticate.
    • copilot_studio_connect: description changed.

    Why it could matter

    • An existing tool name now declares stronger authority, so a configuration that allowed it before may allow more now.
    • Calls or consumers built for the earlier schema may need to change.
    • Models choose and call tools partly from their descriptions.

    What to verify

    • Re-confirm whether agents should keep access to this tool.
    • Validate representative existing tool calls against the new argument schema.
    • Spot-check that agents still select this tool as intended.
    Declared effect
    write → write
    Description
    PreviousOpen Microsoft work-account sign-in when status says signedIn:false, the user explicitly requests reconnection/account change, or an authentication error requires interactive sign-in. This signs in only; copilot_studio_select_environment establishes the cloud service connection. When signedIn is false, call this directly as part of carrying out the user's request: the browser sign-in prompt is the user's own confirmation, so do not ask for separate approval in chat first. Ask first only when this would replace an existing signed-in session, because that clears the current account, environment and connector setup plans. Do not call for an already-ready session merely to start another task, or just to select an environment.
    CurrentSign in when signedIn:false; otherwise acquire an MCP token silently, possibly from cache, and retain the current account and environment. This does not force token refresh, validate service access, or clear an HTTP 401. This signs in only; copilot_studio_select_environment establishes the cloud service connection. When signedIn is false, the browser prompt is the user's confirmation, so do not ask for separate approval in chat first. Set reauthenticate:true only after the user requests account change, agrees to a required interactive sign-in, or approves one interactive attempt after an MCP HTTP 401 repeats following successful silent acquisition; this will replace an existing signed-in session and clear its environment and setup plans. The account picker may select a different account or tenant; confirm the returned identity before selecting an environment. A new sign-in may not fix service permissions; if it is still rejected, stop/report rather than looping. Never automatically replay the failed operation. Do not call for an already-ready session merely to start another task, or just to select an environment. A transient token error is not a request to reauthenticate.

    Input schema

    PropertyPrevious (1.0.2)Current (1.0.4)Change
    reauthenticatenot presentbooleanoptional
    • Added
    1 unchanged entry
    • (schema root)

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  2. copilot_studio_disconnectModifiedDescriptionINFO

    What changed

    • copilot_studio_disconnect: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    write → write
    Description
    PreviousClose the cloud service connection, sign out locally, and clear the environment selection and connector setup plans. Does not delete connector connections or modify any online artifact.
    CurrentClose the cloud service connection, sign out locally, and clear the environment selection and connector setup plans. Also removes the sign-in and environment remembered for new chats on this service deployment, so other open chats sharing it must sign in again. Does not delete connector connections or modify any online artifact.

    Input schema

    Input schema unchanged.

    1 unchanged entry
    • (schema root)

    No output schema is recorded for this tool in either release.

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
7 tools with no recorded change
  • copilot_studio_clear_read_cache
  • copilot_studio_connection_setup_status
  • copilot_studio_list_environments
  • copilot_studio_prepare_connection
  • copilot_studio_select_environment
  • copilot_studio_setup_connection
  • copilot_studio_status

Evidence and provenance

Static findings
FAIL from Modelara’s automated analysis of the two declared interfaces. A policy outcome, not a security rating or a runtime test.
Human review
Pending human review. No reviewer decision is recorded for this comparison.
Published evidence
Part of Valyd’s published data generation listed in valyd-data-source.json. Published records are not rewritten.
Show provenance and exact files
Comparison
microsoft-copilot-studio/1.0.2~1.0.4The published comparison identifier.
Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 16, 2026, 10:16 PM UTC.
Distribution
npm
Previous release
@microsoft/copilot-studio-mcp@1.0.29 tools · published by the registry Oct 19, 2026, 6:55 PM UTCArtifact integritysha512-Tos9050gSq332EXXLyVitdqMMXfZsW+VBsTVUDWeWSpxh/1ILBNquSzOGt5G+9BiDOSEFSfUEMRox/fiwHLuUQ==Interface fingerprintsha256:2c4c0675b9a3e2e9c4c97fbfd5d5f8f744892b695cc99e2b2da0b3cefe9b1cffExact interface snapshot (JSON)
Current release
@microsoft/copilot-studio-mcp@1.0.49 tools · published by the registry Nov 10, 2026, 7:36 PM UTCArtifact integritysha512-tIPLXIft4Lru4WJXLe+mjNzYIatcIJfPGa6QCCXXhSFMOdnHv/KI2hSx/M1t0++tRgBCsyIFCRxayS5ybozRZg==Interface fingerprintsha256:41173c31719d18531ad6fecba1a43ffed84e29ba7b66756eb946ba83132a5436Exact interface snapshot (JSON)

The integrity value or digest identifies the exact artifact that was inspected; it does not show that the package is safe. The interface fingerprint identifies the declared tools and schemas Modelara recorded for that release.

MODELARA ANALYSIS OUTPUT

Interface findings

Analyzed with Modelara v0.1.8 · Nov 16, 2026

Policy failures

1 finding
  • copilot_studio_connectFAILChanged

    Declared effect write → destructive

    Authority
    WRITEDESTRUCTIVE

Requires review

1 finding
  • copilot_studio_connectREVIEWChanged

    Input schema changed

    Show details
    • input property added: reauthenticate
    Authority
    WRITEDESTRUCTIVE

Informational

2 findings
  • copilot_studio_connectINFOChanged

    Description changed

    Authority
    WRITEDESTRUCTIVE
  • copilot_studio_disconnectINFOChanged

    Description changed

    Authority
    WRITEWRITE
    Authority unchanged
What do these results mean?
PASS
No policy-significant interface change detected.
REVIEW
Interface changes require inspection.
FAIL
A policy-significant change was detected.
INVALID
The comparison could not be evaluated reliably.
← Back to Copilot Studio release history