DescribePhishByField
[incident] 按条件统计钓鱼分类信息，支持时间,告警名称，私有化调用path为：capi/SecurityOpenApi/DescribePhishByField
This record as markdown: /tools/ioacloud-ioacloud-mcp/describephishbyfield.md
What DescribePhishByField does on Ioacloud
AI agents call DescribePhishByField 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）(只支持32位) |
EndTime | number | — | 结束时间 |
Filters | array | — | PhishRiskTitle - string 是否必填： 否 - 操作符： eq, like PhishDetails - string 是否必填： 否 - 操作符： eq,like Name - string 是否必填： 否 - 操作符：like PhishFile - string 是否必填： 否 - 操作符： |
StartTime | number | — | 开始时间 |
Parameters from the server's own tool schema.
Why DescribePhishByField is rated Low
Even though DescribePhishByField 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 DescribePhishByField 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 DescribePhishByField, this is the rule to start with:
DescribePhishByField 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 DescribePhishByField call is checked against it from then on.
Questions about DescribePhishByField
[incident] 按条件统计钓鱼分类信息，支持时间,告警名称，私有化调用path为：capi/SecurityOpenApi/DescribePhishByField. It is categorised as a Read tool in the Ioacloud MCP Server, which means it retrieves data without modifying state.
DescribePhishByField accepts 4 parameters: OsType, EndTime, Filters, StartTime. 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 DescribePhishByField: 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.
DescribePhishByField 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 DescribePhishByField 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 DescribePhishByField. 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.
DescribePhishByField 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