search_content_browser
A read tool on the Uefn MCP server.
This record as markdown: /tools/quangdang46-uefn-verse-mcp/search-content-browser.md
What search_content_browser does on Uefn
AI agents call search_content_browser to retrieve information from Uefn without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why search_content_browser is rated Low
The name suggests a search operation that retrieves or queries data from UEFN's content browser without modifying anything. However, confidence is moderate (0.7) because the description is empty, and without additional context about what this search returns or enables, there is some uncertainty.
From the tool's definition Tool name 'search_content_browser' indicates querying/searching the Unreal Editor's content browser for assets or data.
Attacks that exploit this kind of access
The rule that runs search_content_browser safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Uefn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_content_browser, this is the rule to start with:
search_content_browser is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Uefn, apply this rule, and every search_content_browser call is checked against it from then on.
Questions about search_content_browser
search_content_browser is a read tool on the Uefn MCP server. It is categorised as a Read tool in the Uefn MCP Server, which means it retrieves data without modifying state.
Register the Uefn MCP server in PolicyLayer and add a rule for search_content_browser: 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 Uefn. Nothing to install.
search_content_browser 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_content_browser 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_content_browser. 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_content_browser is provided by the Uefn MCP server (quangdang46/uefn-verse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Uefn, and thousands of servers like it.
This server
Across the catalogue