manage_cache_health · Material 3 MCP Server MCP

WHAT IT DOES

What manage_cache_health does on Material 3 MCP Server

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

WHY IT NEEDS A POLICY

Why manage_cache_health needs a policy

An AI agent can call manage_cache_health faster than any human can review — one bad instruction and it creates or modifies resources in Material 3 MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_cache_health Rate-limited

manage_cache_health 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": {
    "manage_cache_health": {
      "limits": [
        {
          "counter": "manage_cache_health_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 Material 3 MCP Server, so you can run agents against it safely.

FAQ

Questions about manage_cache_health

What does the manage_cache_health tool do? +

Check cache status, verify upstream changes, and invalidate stale data. It is categorised as a Write tool in the Material 3 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on manage_cache_health? +

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

What risk level is manage_cache_health? +

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

Can I rate-limit manage_cache_health? +

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

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

manage_cache_health is provided by the Material 3 MCP Server MCP server (weppa-cloud/material3-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.