DescribeUEBAUnauthorizedAccess
[incident] UEBA风险分析日志详情-访问未授权业务记录，私有化调用path为：capi/LogCenter/DescribeUEBADetail/UnauthorizedAccess 前置：DescribeUEBAEvents 定位事件 + DescribeLocalAccounts 拿 UserId + DescribeAccountGroups 拿 AccountGroupId。
This record as markdown: /tools/ioacloud-ioacloud-mcp/describeuebaunauthorizedaccess.md
What DescribeUEBAUnauthorizedAccess does on Ioacloud
AI agents call DescribeUEBAUnauthorizedAccess 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 |
|---|---|---|---|
LogId | string | Yes | 日志ID |
UserId | string | Yes | 用户Id |
PageSize | number | Yes | 分页大小(只支持32位) |
PageNumber | number | Yes | 分页(只支持32位) |
AccountGroupId | number | Yes | 账号组Id |
UnauthorizedAccessCount | number | Yes | 详情页接口UnauthorizedAccessCount |
UnauthorizedAccessTimestamps | object | — | 详情页接口UnauthorizedAccessTimestamps |
Parameters from the server's own tool schema.
Why DescribeUEBAUnauthorizedAccess is rated Low
Even though DescribeUEBAUnauthorizedAccess 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.
Attacks that exploit this kind of access
The rule that runs DescribeUEBAUnauthorizedAccess 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 DescribeUEBAUnauthorizedAccess, this is the rule to start with:
DescribeUEBAUnauthorizedAccess 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 DescribeUEBAUnauthorizedAccess call is checked against it from then on.
Questions about DescribeUEBAUnauthorizedAccess
[incident] UEBA风险分析日志详情-访问未授权业务记录，私有化调用path为：capi/LogCenter/DescribeUEBADetail/UnauthorizedAccess 前置：DescribeUEBAEvents 定位事件 + DescribeLocalAccounts 拿 UserId + DescribeAccountGroups 拿 AccountGroupId。. It is categorised as a Read tool in the Ioacloud MCP Server, which means it retrieves data without modifying state.
DescribeUEBAUnauthorizedAccess accepts 7 parameters: LogId, UserId, PageSize, PageNumber, AccountGroupId, UnauthorizedAccessCount, UnauthorizedAccessTimestamps. Required: LogId, UserId, PageSize, PageNumber, AccountGroupId, UnauthorizedAccessCount. 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 DescribeUEBAUnauthorizedAccess: 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.
DescribeUEBAUnauthorizedAccess 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 DescribeUEBAUnauthorizedAccess 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 DescribeUEBAUnauthorizedAccess. 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.
DescribeUEBAUnauthorizedAccess 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