列出所有可用的KPC组件或按分类筛选
AI agents call list_kpc_components to retrieve information from KPC Component Library MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists component metadata without modifying state, executing code, or causing side effects. It is a straightforward read operation that returns information about available components in the KPC library, making it a low-risk Read category tool.
From the tool's definition Tool name 'list_kpc_components' and description '列出所有可用的KPC组件或按分类筛选' (list all available KPC components or filter by category) indicate a retrieval/query operation. No modification, deletion, execution, or financial impact is described.
Attacks that exploit this kind of access
列出所有可用的KPC组件或按分类筛选. It is categorised as a Read tool in the KPC Component Library MCP Server MCP Server, which means it retrieves data without modifying state.
Register the KPC Component Library MCP Server MCP server in PolicyLayer and add a rule for list_kpc_components: 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 KPC Component Library MCP Server. Nothing to install.
list_kpc_components 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 list_kpc_components 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 list_kpc_components. 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.
list_kpc_components is provided by the KPC Component Library MCP Server MCP server (kregyu/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 →