refresh_cache · Ontario Data MCP: Risk & Policy

WHAT IT DOES

What refresh_cache does on Ontario Data

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

WHY IT NEEDS A POLICY

Why refresh_cache needs a policy

This tool overwrites existing cached data with freshly downloaded versions. It is a reversible write operation (cache can be refreshed again), not a destructive permanent deletion. It modifies stored state by replacing cached files, making Write the most appropriate category.

From the tool's definition Re-download cached resources to get the latest data

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

refresh_cache Rate-limited

refresh_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": {
    "refresh_cache": {
      "limits": [
        {
          "counter": "refresh_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 Ontario Data, so you can run agents against it safely.

FAQ

Questions about refresh_cache

What does the refresh_cache tool do? +

Re-download cached resources to get the latest data. It is categorised as a Write tool in the Ontario Data MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on refresh_cache? +

Register the Ontario Data 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 Ontario Data. Nothing to install.

What risk level is refresh_cache? +

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

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 Ontario Data MCP server (sprine/ontario-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.