DescribeDeviceCompliantInfos
[device] 获取未合规设备列表信息，私有化调用path为：/capi/SecurityOpenApi/CompliantDevice/DescribeDeviceCompliantInfos 前置：DescribeDevices 拿 Mid。
This record as markdown: /tools/ioacloud-ioacloud-mcp/describedevicecompliantinfos.md
What DescribeDeviceCompliantInfos does on Ioacloud
AI agents call DescribeDeviceCompliantInfos to retrieve information from Ioacloud without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
OsType | number | — | 系统类型（0: win，1：linux，2: mac，3: win_srv，4：android，5：ios 默认值0） |
GroupId | number | Yes | 设备组id |
Condition | object | — | 滤条件、分页参数 Name - String - 是否必填：否 - 操作符: eq like ilike - 排序支持：是 - 按照设备名排序。 UserName - String - 是否必填：否 - 操作符: eq like ilike - 排序支持：是 - 按照设备用户名排序。 IoaUserName - Str |
RiskLevel | number | — | Comment: 合规风险，0：未开启合规检测设备，1：已合规设备，2：未合规设备，50：低危，200:中危，500:高危 非必传，不传默认为0 |
OnlineStatus | number | — | 在线状态，0：全部，1：离线，2：在线(只支持32位) |
ResultStatus | number | — | 合规状态，0：未开启合规检测设备，1：已合规设备，2：未合规设备，3:未知状态（开启的合规检测子项中没有不合规的结果，但是有一项检测失败）-1：全部设备，非必传，不传默认为0(只支持32位) |
DomainInstanceId | string | — | 管理域实例ID，用于CAM管理域权限分配。若企业未进行管理域的划分，可直接传入根域"1"，此时表示针对当前企业的全部设备和账号进行接口CRUD，具体CRUD的影响范围限制于相应接口的入参。 |
Parameters from the server's own tool schema.
Why DescribeDeviceCompliantInfos is rated Low
Even though DescribeDeviceCompliantInfos only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (31 properties)
Attacks that exploit this kind of access
The rule that runs DescribeDeviceCompliantInfos safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ioacloud, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For DescribeDeviceCompliantInfos, this is the rule to start with:
DescribeDeviceCompliantInfos is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ioacloud, apply this rule, and every DescribeDeviceCompliantInfos call is checked against it from then on.
Questions about DescribeDeviceCompliantInfos
[device] 获取未合规设备列表信息，私有化调用path为：/capi/SecurityOpenApi/CompliantDevice/DescribeDeviceCompliantInfos 前置：DescribeDevices 拿 Mid。. It is categorised as a Read tool in the Ioacloud MCP Server, which means it retrieves data without modifying state.
DescribeDeviceCompliantInfos accepts 7 parameters: OsType, GroupId, Condition, RiskLevel, OnlineStatus, ResultStatus, DomainInstanceId. Required: GroupId. The full parameter table on this page comes from the server's own tool schema.
Register the Ioacloud MCP server in PolicyLayer and add a rule for DescribeDeviceCompliantInfos: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Ioacloud. Nothing to install.
DescribeDeviceCompliantInfos is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the DescribeDeviceCompliantInfos rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for DescribeDeviceCompliantInfos. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
DescribeDeviceCompliantInfos is provided by the Ioacloud MCP server (@ioacloud/ioacloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ioacloud, and thousands of servers like it.
This server
Across the catalogue