AI agents call search_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.
Searching logs is a read-only operation that retrieves existing data with no side effects. While logs may contain sensitive information about game sessions, the action itself is passive retrieval. The severity is low because log access is typically non-destructive and informational, though confidence is very high given the explicit 'search' verb and 'logs' domain.
From the tool's definition Tool name 'search_logs' and description 'Search through FoundryVTT logs' indicate a query-only operation that retrieves log data without modification or execution.
Documented attack patterns abuse exactly the kind of access search_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 search_logs:
{
"version": "1",
"default": "deny",
"tools": {
"search_logs": {}
}
}search_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.
Search through FoundryVTT logs. 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 search_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.
search_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 search_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 search_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.
search_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.