refresh_world_data

THE RISK

Low Risk

Why refresh_world_data needs a policy

The tool explicitly performs a re-fetch operation, which is a read/retrieval action with no described side effects. It refreshes cached data by pulling from the server, not modifying or deleting anything. Severity is low as it only queries data, though repeated calls could have minor performance impact.

From the tool's definition Force re-fetch of world data from the FoundryVTT server

Documented attack patterns abuse exactly the kind of access refresh_world_data gives an agent:

POLICY

How to control refresh_world_data

PolicyLayer is an MCP gateway — it sits between your AI agents and FoundryVTT MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for refresh_world_data:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "refresh_world_data": {}
  }
}

refresh_world_data is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register FoundryVTT MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More FoundryVTT MCP Server tools

Destructive delete_actor_item Delete an item owned by an actor (requires FOUNDRY_WRITE_ENABLED + active Socket.IO connec Execute roll_dice Roll dice using standard RPG notation (e.g., 1d20, 3d6+4) Write create_actor_item Create an item on an actor from an inline item document (requires FOUNDRY_WRITE_ENABLED + Write generate_loot Generate random loot for encounters Write generate_npc Generate a random NPC with stats and background Write update_actor_attributes Update attributes on an actor Read diagnose_errors Stub: returns raw logs without analysis. Full diagnostic logic is tracked in 133 and not y Read get_actor_details Get detailed information about a specific actor

All 25 FoundryVTT MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about refresh_world_data

What does the refresh_world_data tool do? +

Force re-fetch of world data from the FoundryVTT server. It is categorised as a Read tool in the FoundryVTT MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on refresh_world_data? +

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

What risk level is refresh_world_data? +

refresh_world_data is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit refresh_world_data? +

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

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

refresh_world_data is provided by the FoundryVTT MCP Server MCP server (laurigates/foundryvtt-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every FoundryVTT MCP Server tool call.

Start from FoundryVTT MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →