Get installation commands and setup instructions for a component
AI agents call get_installation_info to retrieve information from Aceternityui without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns installation information (commands and instructions) for UI components. It does not execute the commands, modify component data, or trigger installations—it merely provides the instructional content. This is a pure read operation with no side effects, placing it in the Read category with low severity.
From the tool's definition Tool name 'get_installation_info' and description 'Get installation commands and setup instructions for a component' indicate retrieval of informational content only.
Documented attack patterns abuse exactly the kind of access get_installation_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Aceternityui, and nothing reaches the server without passing your rules. This is the rule we recommend for get_installation_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_installation_info": {}
}
}get_installation_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get installation commands and setup instructions for a component. It is categorised as a Read tool in the Aceternityui MCP Server, which means it retrieves data without modifying state.
Register the Aceternityui MCP server in PolicyLayer and add a rule for get_installation_info: 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 Aceternityui. Nothing to install.
get_installation_info 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_installation_info 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_installation_info. 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_installation_info is provided by the Aceternityui MCP server (rudra016/aceternityui-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Aceternityui, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Aceternityui tools catalogued and risk-classified — across an index of 43,000+ MCP servers.