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...
Risk signalsAccepts file system path (path)
Part of the Project server.
Free to start. No card required.
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.
Without a policy, an AI agent could call generate_page repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Project.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"generate_page": {
"limits": [
{
"counter": "generate_page_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Project policy for all 10 tools.
These attack patterns abuse exactly the kind of access generate_page gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
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.
Register the Project MCP server in PolicyLayer and add a rule for generate_page: 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 Project. Nothing to install.
generate_page 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 generate_page 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 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.
generate_page is provided by the Project MCP server (project-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 Project tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.