AI agents call get_recent_logs 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 historical log data from the FoundryVTT system. It is a read-only operation that queries existing logs without creating, modifying, deleting, or executing any actions. The worst-case misuse would be information disclosure of log contents, which is low severity in a gaming context.
From the tool's definition Tool name 'get_recent_logs' and description 'Get recent log entries from FoundryVTT' indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_recent_logs 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_recent_logs:
{
"version": "1",
"default": "deny",
"tools": {
"get_recent_logs": {}
}
}get_recent_logs 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 recent log entries from FoundryVTT. 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_recent_logs: 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_recent_logs 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_recent_logs 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_recent_logs. 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_recent_logs 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.