Add an item from the registry to the user
AI agents use add_item to create or update resources in Shadcn Registry manager — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Shadcn Registry manager environment.
This tool modifies the user's project by introducing new items from the registry, which is reversible (items can typically be removed). It does not delete data (not Destructive), execute arbitrary code (not Execute in the dangerous sense—while it may trigger installation logic, the scope is constrained to adding specific registry items), involve financial transactions (not Financial), or merely read data (not Read).
From the tool's definition Tool name 'add_item' combined with description 'Add an item from the registry to the user' indicates creation/modification of project state by adding registry items (components, utilities, etc.) to a Shadcn UI project.
Attacks that exploit this kind of access
Add an item from the registry to the user. It is categorised as a Write tool in the Shadcn Registry manager MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Shadcn Registry manager MCP server in PolicyLayer and add a rule for add_item: 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 Shadcn Registry manager. Nothing to install.
add_item is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_item 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 add_item. 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.
add_item is provided by the Shadcn Registry manager MCP server (reuvenaor/shadcn-registry-manager). 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 →