developer-tools Static interface comparison

CloudBase

2.37.6 2.37.7

PASSAutomated static analysis

No policy-significant interface change detected.

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.

Tools42 → 42
Added0
Removed0
Schema changes0
Input schema changes0
Output schema changes0
Unclassified schema changes0
Description changes2
New write authority0
New destructive authority0
New unknown authority0
AnalysisPASS

INTERFACE DIFF

What changed, tool by tool

Classification from the recorded findings · definitions from the published snapshots

2 tools with recorded changes

  1. managePermissionsModifiedDescriptionINFO

    What changed

    • managePermissions: 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
    Previous管理 CloudBase 权限与用户配置,支持修改资源权限(数据库/云函数/存储桶等)、角色管理、成员与策略增删、应用用户 CRUD,以及设置网关 OPA Rego 策略(对齐 CLI `tcb policy set`)。 示例: - 设置存储桶为私有:`action="updateResourcePermission", resourceType="storage", resourceId="bucket-name", permission="PRIVATE"` - 创建角色:`action="createRole", roleName="admin", roleIdentity="admin"` - 放开云函数匿名/未登录访问(PG 会走 OPA,对齐 CLI `tcb policy set`):`action="updateResourcePermission", resourceType="function", resourceId="myFn", permission="CUSTOM", securityRule='{"invoke":true}'` - 直接设置用户 Rego:`action="setPolicy", regoContent="package authz.user\n\ndefault allow := false\n", confirm=true`(⚠️ 立即禁用旧网关鉴权) 注意:`createUser` / `updateUser` 是环境侧应用用户管理能力,适合测试账号、管理员或预置用户,不应替代浏览器里的 Web SDK 注册表单;前端用户名密码注册应使用 `auth.signUp({ username, password })`,登录应使用 `auth.signInWithPassword({ username, password })`。直接在浏览器里用 `auth.signUp` 创建用户名密码用户取决于 SDK/provider 支持,使用前必须验证;不支持时应走后端或管理端边界,不能在浏览器暴露密钥。`securityRule` 的详细语义取决于 `resourceType`:`doc._openid`、`auth.openid`、查询条件子集校验,以及 `create` / `update` / `delete` JSON 模板仅适用于 `resourceType="noSqlDatabase"` 的文档数据库安全规则;配置 `function` 或 `storage` 时,请参考各自官方安全规则文档,而不是复用 NoSQL 模板。 📌 跨后端边界提示:调用前先用 `queryEnv(action="info", envId=...)` 看 `EnvInfo.RuntimeBackends`: - `resourceType="noSqlDatabase"` 仅作用于 CloudBase NoSQL 文档数据库的集合;CloudBase PostgreSQL(PG)表的行级权限**不**受它控制——PG 表请改用 RLS:`managePgDatabase(action="execute", confirm=true)` 跑 `ALTER TABLE ... ENABLE ROW LEVEL SECURITY` 与 `CREATE POLICY ...`。同一个 PG 环境里如果还有 NoSQL 集合在用,对那些**集合**继续使用 `noSqlDatabase` 规则是正确的——不是"PG 环境就禁用本工具"。 - `resourceType="storage"` 控制的是 NoSQL/COS 存储桶 ACL;PG 的 `pgstore` bucket 不在此 `resourceType` 覆盖范围内。 - 本工具不涉及 MySQL;MySQL 数据库权限请走 MySQL 自身的 GRANT/REVOKE 语句(通过 `manageMysqlDatabase`)。 ⚠️ PostgreSQL 环境:平台 `ModifyResourcePermission` 对 PG 环境会直接拒绝。当 `resourceType="function"` 时,本工具会自动回退到 Manager SDK `modifyEnvAuthzConfig`(与 CLI `tcb policy set` 一致,写入 `authz.user.rego`)。`securityRule` 可传完整 Rego(`package authz.user`)或 `'{"invoke":true}'`(自动生成放通 anonymous/unauthenticated 调 functions 的策略)。设置 Rego 后旧网关鉴权会失效,行为与 CLI 相同。显式 OPA 策略请优先用 `action="setPolicy"`。 ⚠️ 角色类 action(`createRole` / `deleteRoles` / `updateRole`)在 **PostgreSQL 类型环境**下平台侧一律拒绝(`The current API does not support PostgreSQL type environments.`)——平台能力边界,不是配置问题,**不要在 PG 环境反复重试**;PG 环境请改用 RLS(`managePgDatabase(action="execute")` 跑 `CREATE POLICY`)或控制台管理权限。
    Current管理 CloudBase 权限与用户配置,支持修改资源权限(数据库/云函数/存储桶等)、角色管理、成员与策略增删、应用用户 CRUD,以及设置网关 OPA Rego 策略(对齐 CLI `tcb policy set`)。 示例: - 设置存储桶为私有:`action="updateResourcePermission", resourceType="storage", resourceId="bucket-name", permission="PRIVATE"` - 创建角色:`action="createRole", roleName="admin", roleIdentity="admin"` - 放开云函数匿名/未登录访问(PG 会走 OPA,对齐 CLI `tcb policy set`):`action="updateResourcePermission", resourceType="function", resourceId="myFn", permission="CUSTOM", securityRule='{"invoke":true}'` - 直接设置用户 Rego:`action="setPolicy", regoContent="package authz.user\n\ndefault allow := false\n", confirm=true`(⚠️ 立即禁用旧网关鉴权) 注意:`createUser` / `updateUser` 是环境侧应用用户管理能力,适合测试账号、管理员或预置用户,不应替代浏览器里的 Web SDK 注册表单;前端用户名密码注册应使用 `auth.signUp({ username, password })`,登录应使用 `auth.signInWithPassword({ username, password })`。直接在浏览器里用 `auth.signUp` 创建用户名密码用户取决于 SDK/provider 支持,使用前必须验证;不支持时应走后端或管理端边界,不能在浏览器暴露密钥。`securityRule` 的详细语义取决于 `resourceType`:`doc._openid`、`auth.openid`、查询条件子集校验,以及 `create` / `update` / `delete` JSON 模板仅适用于 `resourceType="noSqlDatabase"` 的文档数据库安全规则;配置 `function` 或 `storage` 时,请参考各自官方安全规则文档,而不是复用 NoSQL 模板。 📌 跨后端边界提示:调用前先用 `queryEnv(action="info", envId=...)` 看 `EnvInfo.RuntimeBackends`: - `resourceType="noSqlDatabase"` 仅作用于 CloudBase NoSQL 文档数据库的集合;CloudBase PostgreSQL(PG)表的行级权限**不**受它控制——PG 表请改用 RLS:`managePgDatabase(action="execute", confirm=true)` 跑 `ALTER TABLE ... ENABLE ROW LEVEL SECURITY` 与 `CREATE POLICY ...`。同一个 PG 环境里如果还有 NoSQL 集合在用,对那些**集合**继续使用 `noSqlDatabase` 规则是正确的——不是"PG 环境就禁用本工具"。 - `resourceType="storage"` 控制的是 NoSQL/COS 存储桶 ACL;PG 的 `pgstore` bucket 不在此 `resourceType` 覆盖范围内。 - 本工具不涉及 MySQL;MySQL 数据库权限请走 MySQL 自身的 GRANT/REVOKE 语句(通过 `manageMysqlDatabase`)。 ⚠️ PostgreSQL 环境:平台 `ModifyResourcePermission` 对 PG 环境会直接拒绝。当 `resourceType="function"` 时,本工具会自动回退到 Manager SDK `modifyEnvAuthzConfig`(与 CLI `tcb policy set` 一致,写入 `authz.user.rego`)。`securityRule` 可传完整 Rego(`package authz.user`)或 `'{"invoke":true}'`(自动生成放通 anonymous/unauthenticated 调 functions 的策略)。设置 Rego 后会替换该环境整个用户策略文档(对全环境生效,不是单个函数/资源),旧网关鉴权立即失效且不会回退,与 CLI 行为一致。显式 OPA 策略请优先用 `action="setPolicy"`。 ⚠️ 角色类 action(`createRole` / `deleteRoles` / `updateRole`)在 **PostgreSQL 类型环境**下平台侧一律拒绝(`The current API does not support PostgreSQL type environments.`)——平台能力边界,不是配置问题,**不要在 PG 环境反复重试**;PG 环境请改用 RLS(`managePgDatabase(action="execute")` 跑 `CREATE POLICY`)或控制台管理权限。

    Input schema

    Input schema unchanged.

    26 unchanged entries
    • (schema root)
    • action
    • confirm
    • description
    • memberUids
    • memberUids › [items]
    • password
    • permission
    • policies
    • policies › [items]
    • policyIds
    • policyIds › [items]
    • regoContent
    • resourceId
    • resourceType
    • roleId
    • roleIdentity
    • roleIds
    • roleIds › [items]
    • roleName
    • securityRule
    • uid
    • uids
    • uids › [items]
    • userStatus
    • username

    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. queryPermissionsModifiedDescriptionINFO

    What changed

    • queryPermissions: 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
    read → read
    Description
    Previous查询 CloudBase 权限与用户配置,支持查询资源权限(数据库/云函数/存储桶等)、角色列表/详情、应用用户列表/详情,以及网关 OPA 授权策略(对齐 CLI `tcb policy list/get`)。 示例: - 查询存储桶权限:`action="getResourcePermission", resourceType="storage", resourceId="bucket-name"` - 列出旧网关策略:`action="listPolicy"`(PG / OPA 引擎环境返回空列表,与 CLI 一致) - 读取用户 Rego:`action="getPolicy"`;平台扩展策略:`action="getPolicy", extension=true` 📌 跨后端边界提示:调用前先用 `queryEnv(action="info", envId=...)` 看 `EnvInfo.RuntimeBackends`。`resourceType="noSqlDatabase"` 查询的是 CloudBase NoSQL 集合规则,与 CloudBase PostgreSQL(PG)表的行级安全(RLS)是两套独立机制——同一个 PG 环境里 NoSQL 集合若仍在使用,对那些集合查询本工具结果**仍然有效**。要查 PG 表 RLS,请改用 `queryPgDatabase(action="sql", sql="SELECT * FROM pg_policies WHERE tablename=...")`。本工具不涉及 MySQL 权限。 ⚠️ PostgreSQL 环境:平台 `DescribeResourcePermission` 对 PG 环境会直接拒绝。当 `resourceType="function"` 时,本工具会自动回退到 Manager SDK `describeEnvAuthzConfig`(与 CLI `tcb policy get` 一致,读取 `authz.user.rego`)。显式 OPA 策略请用 `listPolicy` / `getPolicy`。 ⚠️ 角色类 action(`listRoles` / `getRole`)在 **PostgreSQL 类型环境**下平台侧一律拒绝(`The current API does not support PostgreSQL type environments.`)——这是平台能力边界,不是配置问题,**不要在 PG 环境反复重试**;PG 环境请改用 RLS(`managePgDatabase(action="execute")` 跑 `CREATE POLICY`)或控制台管理权限。
    Current查询 CloudBase 权限与用户配置,支持查询资源权限(数据库/云函数/存储桶等)、角色列表/详情、应用用户列表/详情,以及网关 OPA 授权策略(对齐 CLI `tcb policy list/get`)。 示例: - 查询存储桶权限:`action="getResourcePermission", resourceType="storage", resourceId="bucket-name"` - 列出旧网关策略:`action="listPolicy"`(只有真实查询为空才等于「没有策略」;PG / OPA 引擎环境会跳过查询,返回 `skipped=true` 与空列表,**不代表没有策略**,请改用 getPolicy) - 读取用户 Rego:`action="getPolicy"`;平台扩展策略:`action="getPolicy", extension=true` 📌 跨后端边界提示:调用前先用 `queryEnv(action="info", envId=...)` 看 `EnvInfo.RuntimeBackends`。`resourceType="noSqlDatabase"` 查询的是 CloudBase NoSQL 集合规则,与 CloudBase PostgreSQL(PG)表的行级安全(RLS)是两套独立机制——同一个 PG 环境里 NoSQL 集合若仍在使用,对那些集合查询本工具结果**仍然有效**。要查 PG 表 RLS,请改用 `queryPgDatabase(action="sql", sql="SELECT * FROM pg_policies WHERE tablename=...")`。本工具不涉及 MySQL 权限。 ⚠️ PostgreSQL 环境:平台 `DescribeResourcePermission` 对 PG 环境会直接拒绝。当 `resourceType="function"` 时,本工具会自动回退到 Manager SDK `describeEnvAuthzConfig`(与 CLI `tcb policy get` 一致,读取 `authz.user.rego`)。显式 OPA 策略请用 `listPolicy` / `getPolicy`。 ⚠️ 角色类 action(`listRoles` / `getRole`)在 **PostgreSQL 类型环境**下平台侧一律拒绝(`The current API does not support PostgreSQL type environments.`)——这是平台能力边界,不是配置问题,**不要在 PG 环境反复重试**;PG 环境请改用 RLS(`managePgDatabase(action="execute")` 跑 `CREATE POLICY`)或控制台管理权限。

    Input schema

    Input schema unchanged.

    15 unchanged entries
    • (schema root)
    • action
    • extension
    • pageNo
    • pageSize
    • policyResourceType
    • resourceId
    • resourceIds
    • resourceIds › [items]
    • resourceType
    • roleId
    • roleIdentity
    • roleName
    • uid
    • username

    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
40 tools with no recorded change
  • auth
  • callCloudApi
  • deployApply
  • deployBuild
  • deployPlan
  • downloadTemplate
  • envDomainManagement
  • manageAgents
  • manageAppAuth
  • manageApps
  • manageCloudRun
  • manageDataModel
  • manageEnv
  • manageFunctions
  • manageGateway
  • manageHosting
  • manageLogs
  • manageMysqlDatabase
  • managePgDatabase
  • manageStorage
  • modifyDataModel
  • prepareFeedback
  • queryAgents
  • queryAppAuth
  • queryApps
  • queryCloudRun
  • queryEnv
  • queryFunctions
  • queryGateway
  • queryHosting
  • queryLogs
  • queryMysqlDatabase
  • queryPgDatabase
  • queryPgStorage
  • queryStorage
  • readNoSqlDatabaseContent
  • readNoSqlDatabaseStructure
  • searchKnowledgeBase
  • writeNoSqlDatabaseContent
  • writeNoSqlDatabaseStructure

Evidence and provenance

Static findings
PASS from Modelara’s automated analysis of the two declared interfaces. A policy outcome, not a security rating or a runtime test.
Human review
Automated static analysis. 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
tencentcloudbase-cloudbase-mcp/2.37.6~2.37.7The published comparison identifier.
Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 16, 2026, 11:28 PM UTC.
Distribution
npm
Previous release
@cloudbase/cloudbase-mcp@2.37.642 tools · published by the registry Nov 11, 2026, 8:10 AM UTCArtifact integritysha512-9C358nkf+4P8aeg6CJCHS7BvWV1UINCUPi+OKMO3kHRbDGHx9YZqOivF/9EoVdZTT90NFs3MoKTZKwDEC00Pug==Interface fingerprintsha256:496918b4106c619f232f4f04735fd9231e1dc164bcafd522e8e2c3399acebd72Exact interface snapshot (JSON)
Current release
@cloudbase/cloudbase-mcp@2.37.742 tools · published by the registry Nov 16, 2026, 6:41 AM UTCArtifact integritysha512-S+4f16nV5FGfQbt6JmNm6NuFoNqy2f+oUb/eMEYnOjG7IUyZZeHBsOfXaIHkQng82RSH82H3B9LXG7qic4rK6A==Interface fingerprintsha256:d43bc2a8661c217f5db93a2666461c29da1cf370045bfe36118c20975327c47dExact 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

Informational

2 findings
  • managePermissionsINFOChanged

    Description changed

    Authority
    DESTRUCTIVEDESTRUCTIVE
    Authority unchanged
  • queryPermissionsINFOChanged

    Description changed

    Authority
    READREAD
    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 CloudBase release history