generate_page

Accepts file system path (path)

Part of the Project MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

// WHEN AI AGENTS USE THIS TOOL

AI agents use generate_page to create or modify resources in Project. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON GENERATE_PAGE

Without a policy, an AI agent could call generate_page repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Project.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

project.yaml

tools:
  generate_page:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Project policy for all 10 tools.

// DETAILS

Tool Name generate_page

Category Write

MCP Server Project MCP Server

Risk Level Medium

// MORE PROJECT TOOLS

Execute env_run_check Write generate_action Write generate_component Read env_prisma_status Read env_status Read project_actions Read project_models Read project_routes

View all 10 tools →

// WHAT CAN GO WRONG

Agents calling write-class tools like generate_page have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the generate_page tool do? +

Genera una página Next.js 16 siguiendo el patrón del proyecto: - RSC por defecto - Metadata dinámica si necesita SEO - Layout con estructura del dashboard si es una ruta protegida - Suspense boundaries y loading state Args: - path: ruta de la página (ej: "/dashboard/users/[id]") - type: tipo de página - with_auth: si requiere sesión (agrega redirect si no hay sesión) Returns: código de la página listo para src/app/[ruta]/page.tsx. It is categorised as a Write tool in the Project MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_page? +

Add a rule in your Intercept YAML policy under the tools section for generate_page. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Project MCP server.

What risk level is generate_page? +

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

Can I rate-limit generate_page? +

Yes. Add a rate_limit block to the generate_page rule in your Intercept 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 generate_page completely? +

Set action: deny in the Intercept policy for generate_page. 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 generate_page? +

generate_page is provided by the Project MCP server (project-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

generate_page

Enforce policies on Project