DescribeLogDetailResourceAccess
[log] 日志详情查询 前置：DescribeLogCondition。
This record as markdown: /tools/ioacloud-ioacloud-mcp/describelogdetailresourceaccess.md
What DescribeLogDetailResourceAccess does on Ioacloud
AI agents call DescribeLogDetailResourceAccess 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 |
|---|---|---|---|
Sort | object | Yes | 排序 |
LogId | string | Yes | 日志ID UserLogin-用户登录日志 IAMLogin-IAM登录日志 NGNAccess-终端访问日志 Access-代理访问日志 NGNTicket-NGN小票日志 DynamicAccess-动态访问日志 |
OsType | number | — | 终端类型 |
EndTime | number | Yes | 结束时间 |
Filters | array | — | 过滤条件 |
PageSize | number | Yes | 每页数目 |
StartTime | number | Yes | 开始时间 |
Department | number | — | 用户分组 |
PageNumber | number | Yes | 页码 |
EndpointGroup | number | — | 终端分组 |
DomainInstanceId | string | — | 管理域实例ID，用于CAM管理域权限分配 |
Parameters from the server's own tool schema.
Why DescribeLogDetailResourceAccess is rated Low
Even though DescribeLogDetailResourceAccess 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 (17 properties)
Attacks that exploit this kind of access
The rule that runs DescribeLogDetailResourceAccess 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 DescribeLogDetailResourceAccess, this is the rule to start with:
DescribeLogDetailResourceAccess 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 DescribeLogDetailResourceAccess call is checked against it from then on.
Questions about DescribeLogDetailResourceAccess
[log] 日志详情查询 前置：DescribeLogCondition。. It is categorised as a Read tool in the Ioacloud MCP Server, which means it retrieves data without modifying state.
DescribeLogDetailResourceAccess accepts 11 parameters: Sort, LogId, OsType, EndTime, Filters, PageSize, StartTime, Department, PageNumber, EndpointGroup, DomainInstanceId. Required: Sort, LogId, EndTime, PageSize, StartTime, PageNumber. 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 DescribeLogDetailResourceAccess: 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.
DescribeLogDetailResourceAccess 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 DescribeLogDetailResourceAccess 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 DescribeLogDetailResourceAccess. 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.
DescribeLogDetailResourceAccess 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