AI agents use update_actor_attributes 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.
This tool creates or modifies actor data reversibly, fitting the Write category. Severity is high because modifying character attributes can significantly disrupt game sessions—altering abilities, health thresholds, or skill values could break campaign balance or player progression. However, it is not Destructive (changes are reversible via re-update) or Financial.
From the tool's definition Tool name 'update_actor_attributes' explicitly indicates modification of actor data. Description states 'Update attributes on an actor', confirming reversible data modification capability.
Documented attack patterns abuse exactly the kind of access update_actor_attributes 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 update_actor_attributes:
{
"version": "1",
"default": "deny",
"tools": {
"update_actor_attributes": {
"limits": [
{
"counter": "update_actor_attributes_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} update_actor_attributes 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.
Update attributes on an actor. 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 update_actor_attributes: 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.
update_actor_attributes 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 update_actor_attributes 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 update_actor_attributes. 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.
update_actor_attributes 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.