Create an item on an actor from an inline item document (requires FOUNDRY_WRITE_ENABLED + active Socket.IO connection). Compendium-source create is not yet supported over Socket.IO (see issue #159). Canonical target: D&D 5e v4+ activity schema.
AI agents use create_actor_item 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 new items within a game actor (character), which modifies game state but is reversible—items can be deleted via the delete_actor_item tool also present on this server. The severity is medium because while it modifies shared game state that affects other players' sessions, the impact is limited to item management and can be undone.
From the tool's definition Tool name is 'create_actor_item' and description states 'Create an item on an actor from an inline item document'. The verb 'create' and the action of adding items to actors are reversible write operations.
Documented attack patterns abuse exactly the kind of access create_actor_item 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 create_actor_item:
{
"version": "1",
"default": "deny",
"tools": {
"create_actor_item": {
"limits": [
{
"counter": "create_actor_item_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_actor_item 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.
Create an item on an actor from an inline item document (requires FOUNDRY_WRITE_ENABLED + active Socket.IO connection). Compendium-source create is not yet supported over Socket.IO (see issue #159). Canonical target: D&D 5e v4+ activity schema. 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 create_actor_item: 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.
create_actor_item 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 create_actor_item 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 create_actor_item. 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.
create_actor_item 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.