Obtém detalhes completos de um componente (inputs, outputs, selector, uso). Use quando o usuário perguntar sobre um componente específico, seus inputs/outputs, como usar, propriedades, eventos. ⚠️ IMPORTANTE: Forneça exemplo com componente PURO (sem class/style nele). PODE usar CSS em container a...
AI agents call get-component to retrieve information from Angular Component Inspector 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 metadata about Angular components—their inputs, outputs, selectors, and usage patterns. It performs no mutations, executions, deletions, or external operations. It is a pure read operation that queries component definitions from an Angular library's public API exports.
From the tool's definition Tool description states it 'Obtém detalhes completos de um componente' (retrieves complete details of a component) and provides information about inputs, outputs, selector, and usage.
Attacks that exploit this kind of access
Obtém detalhes completos de um componente (inputs, outputs, selector, uso). Use quando o usuário perguntar sobre um componente específico, seus inputs/outputs, como usar, propriedades, eventos. ⚠️ IMPORTANTE: Forneça exemplo com componente PURO (sem class/style nele). PODE usar CSS em container ao redor para apresentação. It is categorised as a Read tool in the Angular Component Inspector MCP Server, which means it retrieves data without modifying state.
Register the Angular Component Inspector MCP server in PolicyLayer and add a rule for get-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 Angular Component Inspector. Nothing to install.
get-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 get-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 get-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.
get-component is provided by the Angular Component Inspector MCP server (marcosviniweb/mcp-poc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get-component is one line of Angular Component Inspector's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →