Get documentation, usage examples, and prop descriptions for a component
AI agents call get_component_docs to retrieve information from its-just-ui 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 queries existing documentation and metadata about components. It performs no modifications, deletions, code execution, or external operations. The action is purely informational and read-only, making it a low-risk Read category tool.
From the tool's definition Tool name 'get_component_docs' and description 'Get documentation, usage examples, and prop descriptions for a component' indicate retrieval of documentation and reference information with no side effects.
Attacks that exploit this kind of access
Get documentation, usage examples, and prop descriptions for a component. It is categorised as a Read tool in the its-just-ui MCP Server MCP Server, which means it retrieves data without modifying state.
Register the its-just-ui MCP Server MCP server in PolicyLayer and add a rule for get_component_docs: 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 its-just-ui MCP Server. Nothing to install.
get_component_docs 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_docs 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_docs. 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_docs is provided by the its-just-ui MCP Server MCP server (its-just-ui/its-just-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 →