manage_cache · QIT MCP Server MCP: Risk & Policy

WHAT IT DOES

What manage_cache does on QIT MCP Server

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

WHY IT NEEDS A POLICY

Why manage_cache needs a policy

Cache manipulation is a write operation that can modify stored data state, potentially affecting subsequent test runs or environment state. However, it is reversible (cache can be refreshed via sync_cache), does not permanently delete data, and does not execute arbitrary code or affect external systems. The impact is scoped to internal cache data, making it Write rather than Execute or Destructive.

From the tool's definition Tool name 'manage_cache' with description indicating 'Low-level QIT cache manipulation.' The description explicitly distinguishes this from 'sync_cache', suggesting direct modification of cached data rather than read-only access.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_cache Rate-limited

manage_cache 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": {
      "limits": [
        {
          "counter": "manage_cache_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 QIT MCP Server, so you can run agents against it safely.

FAQ

Questions about manage_cache

What does the manage_cache tool do? +

Low-level QIT cache manipulation. For refreshing cache data, use sync_cache instead. It is categorised as a Write tool in the QIT 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? +

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

What risk level is manage_cache? +

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

Can I rate-limit manage_cache? +

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

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

manage_cache is provided by the QIT MCP Server MCP server (woocommerce/qit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.