refresh_collection_cache · Directus MCP Server MCP

WHAT IT DOES

What refresh_collection_cache does on Directus MCP Server

AI agents invoke refresh_collection_cache to trigger actions in Directus MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why refresh_collection_cache needs a policy

Refreshing a cache is an operational action that triggers side effects on the server (invalidating and rebuilding cached data). It is not purely reading data, nor is it writing/modifying user data. It executes a system-level operation. Misuse could cause performance degradation or expose stale/inconsistent data temporarily, hence medium severity.

From the tool's definition 'Refresh Directus collection cache' - triggers an external cache invalidation/refresh operation, which is an active system operation beyond simple data retrieval

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

refresh_collection_cache Rate-limited

refresh_collection_cache stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "refresh_collection_cache": {
      "limits": [
        {
          "counter": "refresh_collection_cache_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Directus MCP Server, so you can run agents against it safely.

FAQ

Questions about refresh_collection_cache

What does the refresh_collection_cache tool do? +

Refresh Directus collection cache and verify access. It is categorised as a Execute tool in the Directus MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on refresh_collection_cache? +

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

What risk level is refresh_collection_cache? +

refresh_collection_cache is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit refresh_collection_cache? +

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

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

refresh_collection_cache is provided by the Directus MCP Server MCP server (staminna/mcp-server-claude). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.