AI agents invoke ng_new to trigger actions in Mcp Angular Cli. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes the Angular CLI 'ng new' command, which triggers external operations (project scaffolding, file generation, dependency setup) whose effects depend on arguments like project name and configuration. It is not merely a Read operation (no side effects), Write operation (creates initial project structure as part of external tool execution), or Destructive (not irreversible deletion).
From the tool's definition Tool name 'ng_new' with description 'Run' indicates execution of Angular CLI command to create new projects. The 'ng_new' command scaffolds and initializes a new Angular project, which involves creating files, directories, and executing setup operations.
Documented attack patterns abuse exactly the kind of access ng_new gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Angular Cli, and nothing reaches the server without passing your rules. This is the rule we recommend for ng_new:
{
"version": "1",
"default": "deny",
"tools": {
"ng_new": {
"limits": [
{
"counter": "ng_new_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}ng_new stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Run. It is categorised as a Execute tool in the Mcp Angular Cli MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Angular Cli MCP server in PolicyLayer and add a rule for ng_new: 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 Mcp Angular Cli. Nothing to install.
ng_new is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ng_new 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 ng_new. 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.
ng_new is provided by the Mcp Angular Cli MCP server (talzach/mcp-angular-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Angular Cli, 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 Mcp Angular Cli tools catalogued and risk-classified — across an index of 43,000+ MCP servers.