Get the current active combat state including initiative order, HP, and AC
AI agents call get_combat_state to retrieve information from FoundryVTT MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about ongoing combat (initiative order, hit points, armor class) but does not create, modify, delete, or execute any actions. It has no side effects and poses minimal risk—an AI agent could not cause damage or irreversible harm by calling this tool. The severity is low because misuse would only result in reading information already visible in the game session.
From the tool's definition The tool name 'get_combat_state' and description 'Get the current active combat state including initiative order, HP, and AC' indicate a retrieval operation that queries existing game state data without modification.
Documented attack patterns abuse exactly the kind of access get_combat_state 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 get_combat_state:
{
"version": "1",
"default": "deny",
"tools": {
"get_combat_state": {}
}
}get_combat_state is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the current active combat state including initiative order, HP, and AC. It is categorised as a Read tool in the FoundryVTT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FoundryVTT MCP Server MCP server in PolicyLayer and add a rule for get_combat_state: 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.
get_combat_state is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_combat_state 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 get_combat_state. 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.
get_combat_state 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.