refresh_cache · OpenRouter MCP Server MCP: Risk & Policy

WHAT IT DOES

What refresh_cache does on OpenRouter MCP Server

AI agents invoke refresh_cache to trigger actions in OpenRouter 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_cache needs a policy

This tool triggers an external operation (fetching updated data from OpenRouter and refreshing a local cache). It has side effects beyond a simple read, but does not permanently delete data or move money. It fits Execute as it triggers an external fetch/update operation whose effects depend on the current state of the remote API.

From the tool's definition Force refresh the model cache from OpenRouter

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

refresh_cache Rate-limited

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

FAQ

Questions about refresh_cache

What does the refresh_cache tool do? +

Force refresh the model cache from OpenRouter. It is categorised as a Execute tool in the OpenRouter 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_cache? +

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

What risk level is refresh_cache? +

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

Can I rate-limit refresh_cache? +

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

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

refresh_cache is provided by the OpenRouter MCP Server MCP server (lumishoang/openrouter-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.