Regex search across the current session log buffer.
AI agents call search_logs to retrieve information from Unreal Editor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation: searching and filtering existing log data. It does not create, modify, delete, or execute code/commands. The regex search is applied to already-captured log content, not to external systems. The blast radius of misuse is minimal—an agent could only retrieve information already visible in logs, with no side effects on the Unreal Engine build system or data integrity.
From the tool's definition Tool name 'search_logs' and description 'Regex search across the current session log buffer' indicate querying/retrieving log data with no modification, deletion, or execution of commands.
Attacks that exploit this kind of access
Regex search across the current session log buffer. It is categorised as a Read tool in the Unreal Editor MCP Server, which means it retrieves data without modifying state.
Register the Unreal Editor 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 Unreal Editor. 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 Unreal Editor MCP server (tumourlove/deprecated-unreal-editor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →