Get detailed information about all props used by a specific component. Use this tool when you need to: - Understand what props a component accepts and uses - Document component APIs - Check if a component has certain props before using it - Analyze component interfaces EXAMPLES: 1. Get all props ...
AI agents call get_component_props to retrieve information from JSX Prop Lookup 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 analyzes information about React component prop definitions using AST parsing. It performs no mutations, deletions, code execution, financial transactions, or side effects. It is purely informational analysis of existing codebases, making it a classic Read category tool with low severity risk.
From the tool's definition Tool name is 'get_component_props' and description states it 'Get detailed information about all props used by a specific component' and use cases include 'Understand what props a component accepts', 'Document component APIs', and 'Check if a component has…
Attacks that exploit this kind of access
Get detailed information about all props used by a specific component. Use this tool when you need to: - Understand what props a component accepts and uses - Document component APIs - Check if a component has certain props before using it - Analyze component interfaces EXAMPLES: 1. Get all props for Button component in current directory: {. It is categorised as a Read tool in the JSX Prop Lookup MCP Server MCP Server, which means it retrieves data without modifying state.
Register the JSX Prop Lookup MCP Server MCP server in PolicyLayer and add a rule for get_component_props: 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 JSX Prop Lookup MCP Server. Nothing to install.
get_component_props 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_props 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_props. 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_props is provided by the JSX Prop Lookup MCP Server MCP server (lmn451/jsx-prop-lookup-mcp-server). 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 →