enable_cache_components

// WHEN AI AGENTS USE THIS TOOL

AI agents use enable_cache_components to create or modify resources in Midnight Nextjs. 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 ENABLE_CACHE_COMPONENTS

Without a policy, an AI agent could call enable_cache_components 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 Midnight Nextjs.

// RECOMMENDED POLICY

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

midnight-next-js-mcp.yaml

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

See the full Midnight Nextjs policy for all 35 tools.

// DETAILS

Tool Name enable_cache_components

Category Write

MCP Server Midnight Nextjs MCP Server

Risk Level Medium

// MORE MIDNIGHT NEXTJS TOOLS

Financial midnight_transfer_tokens Destructive browser_eval Destructive init Destructive nextjs_call Destructive nextjs_index Execute midnight_call_contract Execute midnight_compile_contract Execute midnight_deploy_contract

View all 35 tools →

// RELATED READING

// FAQ

What does the enable_cache_components tool do? +

Migrate Next.js applications to Cache Components mode and complete setup for Next.js 16. Use this tool when you need to: - Migrate to Cache Components mode - Migrate to cache components - Enable Cache Components - Set up Cache Components - Convert to Cache Components This tool handles ALL steps for migrating and enabling Cache Components: - Configuration: Updates cacheComponents flag (experimental in 16.0.0, stable in canary > 16), removes incompatible flags - Dev Server: Starts dev server (MCP is enabled by default in Next.js 16+) - Error Detection: Loads all routes via browser automation, collects errors using Next.js MCP - Automated Fixing: Adds Suspense boundaries, "use cache" directives, generateStaticParams, cacheLife profiles, cache tags - Verification: Validates all routes work with zero errors Key Features: - One-time dev server start (no restarts needed) - Automated error detection using Next.js MCP tools - Browser-based testing with browser automation - Fast Refresh applies fixes instantly - Comprehensive fix strategies for all error types - Support for "use cache", "use cache: private", Suspense boundaries - Cache invalidation with cacheTag() and cacheLife() configuration Requires: - Next.js 16.0.0+ (stable or canary only - beta versions are NOT supported) - Clean working directory preferred - Browser automation installed (auto-installed if needed) This tool embeds complete knowledge base for: - Cache Components mechanics - Error patterns and solutions - Caching strategies (static vs dynamic) - Advanced patterns (cacheLife, cacheTag, draft mode) - Build behavior and prefetching - Test-driven patterns from 125+ fixtures. It is categorised as a Write tool in the Midnight Nextjs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on enable_cache_components? +

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

What risk level is enable_cache_components? +

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

Can I rate-limit enable_cache_components? +

Yes. Add a rate_limit block to the enable_cache_components 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 enable_cache_components completely? +

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

enable_cache_components is provided by the Midnight Nextjs MCP server (midnight-nextjs-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Midnight Nextjs