AI agents use generate_loot to create or update resources in FoundryVTT MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FoundryVTT MCP Server environment.
The tool generates (creates) random loot, which modifies the game world by adding new items/content. This is a reversible Write operation—loot can be deleted or modified afterward—making it less severe than Destructive actions. It does not execute arbitrary commands, delete data irreversibly, or move money.
From the tool's definition Tool name 'generate_loot' and description 'Generate random loot for encounters' indicates creation of new game content within the FoundryVTT world. This is a write operation that creates/adds loot data to the game state.
Documented attack patterns abuse exactly the kind of access generate_loot gives an agent:
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 generate_loot:
{
"version": "1",
"default": "deny",
"tools": {
"generate_loot": {
"limits": [
{
"counter": "generate_loot_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}generate_loot 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.
Free to start. No card required.
Generate random loot for encounters. It is categorised as a Write tool in the FoundryVTT MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FoundryVTT MCP Server MCP server in PolicyLayer and add a rule for generate_loot: 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.
generate_loot is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the generate_loot 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.
Set action: deny in the PolicyLayer policy for generate_loot. 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.
generate_loot 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.
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.
Free to start. No card required.
25 FoundryVTT MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.