cache.refresh · Or Info MCP: Risk & Policy

WHAT IT DOES

What cache.refresh does on Or Info

AI agents invoke cache.refresh to trigger actions in Or Info. 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 cache.refresh needs a policy

This tool triggers an external operation — fetching and refreshing data from remote sources (OpenRouter and LMArena) and updating a local cache. It goes beyond a simple read (it modifies the local cache state) and executes an external network operation. It's not purely destructive or financial, but it does trigger side effects (cache invalidation and rewrite), making Execute the most appropriate category.

From the tool's definition Force-refresh the local cache: OpenRouter model catalog + LMArena ELO data

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cache.refresh Rate-limited

cache.refresh 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": {
    "cache.refresh": {
      "limits": [
        {
          "counter": "cache.refresh_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 Or Info, so you can run agents against it safely.

FAQ

Questions about cache.refresh

What does the cache.refresh tool do? +

Force-refresh the local cache: OpenRouter model catalog + LMArena ELO data. It is categorised as a Execute tool in the Or Info MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cache.refresh? +

Register the Or Info MCP server in PolicyLayer and add a rule for cache.refresh: 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 Or Info. Nothing to install.

What risk level is cache.refresh? +

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

Can I rate-limit cache.refresh? +

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

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

cache.refresh is provided by the Or Info MCP server (jmtrs/or-info). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.