Low Risk

get-component-changelog

列出 Ant Design 特定组件的更新日志 适用场景: 1. 用户询问特定组件的更新日志 2. 在知道用户 antd 版本的情况下,当用户需要实现相关组件功能时判断是否在后续版本中才实现,来决定是否需要升级依赖

How to control get-component-changelog ↓

AI agents call get-component-changelog to retrieve information from Antd Components without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries and retrieves component changelog data. It performs a read-only operation that returns version history and update information. There is no data modification, execution of arbitrary code, data deletion, or financial impact. The use cases described confirm it is purely informational retrieval to help users understand component evolution and version compatibility.

From the tool's definition Tool name 'get-component-changelog' and description '列出 Ant Design 特定组件的更新日志' (list Ant Design component changelogs). This retrieves historical information about component updates with no side effects.

Documented attack patterns abuse exactly the kind of access get-component-changelog gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Antd Components, and nothing reaches the server without passing your rules. This is the rule we recommend for get-component-changelog:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-component-changelog": {}
  }
}

get-component-changelog is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Antd Components — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get-component-changelog tool do? +

列出 Ant Design 特定组件的更新日志 适用场景: 1. 用户询问特定组件的更新日志 2. 在知道用户 antd 版本的情况下,当用户需要实现相关组件功能时判断是否在后续版本中才实现,来决定是否需要升级依赖. It is categorised as a Read tool in the Antd Components MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-component-changelog? +

Register the Antd Components MCP server in PolicyLayer and add a rule for get-component-changelog: 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 Antd Components. Nothing to install.

What risk level is get-component-changelog? +

get-component-changelog is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-component-changelog? +

Yes. Add a rate_limit block to the get-component-changelog 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.

How do I block get-component-changelog completely? +

Set action: deny in the PolicyLayer policy for get-component-changelog. 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.

What MCP server provides get-component-changelog? +

get-component-changelog is provided by the Antd Components MCP server (zhixiaoqiang/antd-components-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Antd Components tool call.

Deterministic rules across all 4 Antd Components tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4 Antd Components tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.