UI component tree (pages, containers, leaf components). Layout is Flexbox; special components (LIST/TAB_VIEW/SELECT_VIEW/CONDITIONAL_VIEW) take children only in their built-in slots. Changes apply immediately; use schema_undo to revert the last change. Ops: - op=LIST_PAGES → GET_ALL_PAGE_NAMES - ...
AI agents call schema_component to retrieve information from Zion without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
op | string | Yes | |
appExId | string | null | — | |
componentId | string | — | |
projectExId | string | — | |
appVersionExId | string | null | — |
Parameters from the server's own tool schema.
This tool only queries and retrieves information about UI components, pages, and their properties. The description explicitly states that even modifications 'use schema_undo to revert', indicating changes are managed elsewhere (not by this tool). All four operations are read-only retrieval operations with no side effects, making this a straightforward Read category tool with low risk.
From the tool's definition All operations are GET/LIST queries: 'LIST_PAGES → GET_ALL_PAGE_NAMES', 'GET_CONTEXT_INFO → GET_COMPONENT_CONTEXT_INFO', 'GET_INFO → GET_COMPONENT_INFO', 'GET_CHILDREN_INFO → GET_CONTAINER_CHILDREN_INFO'.
Attacks that exploit this kind of access
UI component tree (pages, containers, leaf components). Layout is Flexbox; special components (LIST/TAB_VIEW/SELECT_VIEW/CONDITIONAL_VIEW) take children only in their built-in slots. Changes apply immediately; use schema_undo to revert the last change. Ops: - op=LIST_PAGES → GET_ALL_PAGE_NAMES - op=GET_CONTEXT_INFO → GET_COMPONENT_CONTEXT_INFO (req: componentId) - op=GET_INFO → GET_COMPONENT_INFO (req: componentId) - op=GET_CHILDREN_INFO → GET_CONTAINER_CHILDREN_INFO (req: componentId). It is categorised as a Read tool in the Zion MCP Server, which means it retrieves data without modifying state.
schema_component accepts 5 parameters: op, appExId, componentId, projectExId, appVersionExId. Required: op. The full parameter table on this page comes from the server's own tool schema.
Register the Zion MCP server in PolicyLayer and add a rule for schema_component: 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 Zion. Nothing to install.
schema_component 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 schema_component 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 schema_component. 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.
schema_component is provided by the Zion MCP server (zion-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 →