module_scaffold_nestjs · LaunchFrame MCP: Risk & Policy

WHAT IT DOES

What module_scaffold_nestjs does on LaunchFrame MCP

AI agents use module_scaffold_nestjs to create or update resources in LaunchFrame MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LaunchFrame MCP environment.

WHY IT NEEDS A POLICY

Why module_scaffold_nestjs needs a policy

This tool generates (creates) new code files — module, service, controller, and entity scaffolds — which is a Write operation. It creates new artifacts in the project but does not execute code, delete anything, or involve financial transactions. Misuse could create unwanted or malformed files, but the blast radius is moderate since generated files can be reviewed and removed.

From the tool's definition Generate a NestJS module scaffold (module + service + optional controller + optional entity) following LaunchFrame conventions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

module_scaffold_nestjs Rate-limited

module_scaffold_nestjs stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "module_scaffold_nestjs": {
      "limits": [
        {
          "counter": "module_scaffold_nestjs_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches LaunchFrame MCP, so you can run agents against it safely.

FAQ

Questions about module_scaffold_nestjs

What does the module_scaffold_nestjs tool do? +

Generate a NestJS module scaffold (module + service + optional controller + optional entity) following LaunchFrame conventions. It is categorised as a Write tool in the LaunchFrame MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on module_scaffold_nestjs? +

Register the LaunchFrame MCP server in PolicyLayer and add a rule for module_scaffold_nestjs: 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 LaunchFrame MCP. Nothing to install.

What risk level is module_scaffold_nestjs? +

module_scaffold_nestjs is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit module_scaffold_nestjs? +

Yes. Add a rate_limit block to the module_scaffold_nestjs 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.

How do I block module_scaffold_nestjs completely? +

Set action: deny in the PolicyLayer policy for module_scaffold_nestjs. 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.

What MCP server provides module_scaffold_nestjs? +

module_scaffold_nestjs is provided by the LaunchFrame MCP server (launchframe-dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.