AI agents call primeng_get_primeng_component to retrieve information from Primeng without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
componentName | string | Yes | Name of the PrimeNG component (e.g., Button, Table, Dialog) |
Parameters from the server's own tool schema.
This tool retrieves documentation for a PrimeNG component, which is a read-only operation that queries existing data without modifying, executing, or deleting anything. The scope is limited to fetching and presenting pre-existing documentation, posing minimal security risk if misused by an AI agent.
From the tool's definition Tool name 'get' and description 'Get documentation for a specific PrimeNG component' indicate retrieval of static documentation without side effects.
Attacks that exploit this kind of access
Get documentation for a specific PrimeNG component. It is categorised as a Read tool in the Primeng MCP Server, which means it retrieves data without modifying state.
primeng_get_primeng_component accepts 1 parameter: componentName. Required: componentName. The full parameter table on this page comes from the server's own tool schema.
Register the Primeng MCP server in PolicyLayer and add a rule for primeng_get_primeng_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 Primeng. Nothing to install.
primeng_get_primeng_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 primeng_get_primeng_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 primeng_get_primeng_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.
primeng_get_primeng_component is provided by the Primeng MCP server (primeng-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 →