Delete an item owned by an actor (requires FOUNDRY_WRITE_ENABLED + active Socket.IO connection). Canonical target: D&D 5e v4+ activity schema.
AI agents call delete_actor_item to permanently remove resources in FoundryVTT MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes items from actor inventories in a tabletop gaming session. While the impact is scoped to a single actor's item (not the entire character or campaign), deletion is irreversible and represents data loss. The high confidence reflects the unambiguous destructive intent in both the name and description.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete an item owned by an actor'. The tool irreversibly removes data from the game state.
Documented attack patterns abuse exactly the kind of access delete_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 delete_actor_item:
{
"version": "1",
"default": "deny",
"hide": [
"delete_actor_item"
]
} delete_actor_item disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete an item owned by an actor (requires FOUNDRY_WRITE_ENABLED + active Socket.IO connection). Canonical target: D&D 5e v4+ activity schema. It is categorised as a Destructive tool in the FoundryVTT MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the FoundryVTT MCP Server MCP server in PolicyLayer and add a rule for delete_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.
delete_actor_item is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.