获取 Element-UI 组件的所有插槽（Slots）信息，包括插槽名称、作用域参数、描述等。
AI agents call get_component_slots to retrieve information from Element-UI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a documentation lookup tool that queries and returns static information about Vue component slots. It follows the same pattern as sibling tools (get_component_props, get_component_events, get_component_methods) which are all informational APIs. There are no write, execute, destructive, or financial operations involved. The blast radius of misuse is minimal since it only exposes component API documentation.
From the tool's definition Tool retrieves documentation about Element-UI component slots (slot names, scope parameters, descriptions).
Attacks that exploit this kind of access
获取 Element-UI 组件的所有插槽（Slots）信息，包括插槽名称、作用域参数、描述等。. It is categorised as a Read tool in the Element-UI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Element-UI MCP Server MCP server in PolicyLayer and add a rule for get_component_slots: 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 Element-UI MCP Server. Nothing to install.
get_component_slots 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 get_component_slots 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 get_component_slots. 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.
get_component_slots is provided by the Element-UI MCP Server MCP server (yun8711/element-ui-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →