High Risk →

refresh_device_catalog

Force rescan the Content Browser and rebuild the dynamic device catalog.

How to control refresh_device_catalog ↓

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.

High Risk

Why refresh_device_catalog needs a policy

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'

Documented attack patterns abuse exactly the kind of access refresh_device_catalog gives an agent:

How to control refresh_device_catalog

PolicyLayer is an MCP gateway — it sits between your AI agents and Uefn, and nothing reaches the server without passing your rules. This is the rule we recommend for refresh_device_catalog:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "refresh_device_catalog": {
      "limits": [
        {
          "counter": "refresh_device_catalog_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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.

  1. Create a free account and register Uefn — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about refresh_device_catalog

What does the refresh_device_catalog tool do? +

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.

How do I enforce a policy on refresh_device_catalog? +

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.

What risk level is refresh_device_catalog? +

refresh_device_catalog is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit refresh_device_catalog? +

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.

How do I block refresh_device_catalog completely? +

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.

What MCP server provides refresh_device_catalog? +

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.

Enforce policy on every Uefn tool call.

Start from Uefn, 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.

143 Uefn tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.