refresh_device_catalog
Force rescan the Content Browser and rebuild the dynamic device catalog.
This record as markdown: /tools/quangdang46-uefn-verse-mcp/refresh-device-catalog.md
What refresh_device_catalog does on Uefn
AI agents invoke refresh_device_catalog to trigger actions in Uefn. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why refresh_device_catalog is rated High
This tool triggers an active operation (force rescan and rebuild) within the UEFN editor environment. It doesn't merely read data—it initiates a rescan and reconstruction process, making it an Execute-category action. Misuse could cause disruption to the editor state or catalog integrity, but is not directly destructive or financial.
From the tool's definition 'Force rescan the Content Browser and rebuild the dynamic device catalog'
Attacks that exploit this kind of access
The rule that runs refresh_device_catalog 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 refresh_device_catalog, this is the rule to start with:
refresh_device_catalog stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 refresh_device_catalog call is checked against it from then on.
Questions about refresh_device_catalog
Force rescan the Content Browser and rebuild the dynamic device catalog. It is categorised as a Execute tool in the Uefn MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Uefn MCP server in PolicyLayer and add a rule for refresh_device_catalog: 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.
refresh_device_catalog is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the refresh_device_catalog 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 refresh_device_catalog. 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.
refresh_device_catalog 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