Medium Risk

save_current_level

Save the current level.

How to control save_current_level ↓

What save_current_level does on Uefn

AI agents use save_current_level to create or update resources in Uefn — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Uefn environment.

Medium Risk

Why save_current_level needs a policy

This tool performs a Write operation: it creates or modifies data reversibly by saving the current state of a level file. While saves are generally recoverable (through version control or undo functionality in UEFN), the operation does persistently alter the project's stored data.

From the tool's definition The tool name is 'save_current_level' and the description states it will 'Save the current level.' This modifies the project state by persisting changes to disk.

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

How to control save_current_level

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 save_current_level:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "save_current_level": {
      "limits": [
        {
          "counter": "save_current_level_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

save_current_level stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about save_current_level

What does the save_current_level tool do? +

Save the current level. It is categorised as a Write tool in the Uefn MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on save_current_level? +

Register the Uefn MCP server in PolicyLayer and add a rule for save_current_level: 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 save_current_level? +

save_current_level is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit save_current_level? +

Yes. Add a rate_limit block to the save_current_level 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 save_current_level completely? +

Set action: deny in the PolicyLayer policy for save_current_level. 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 save_current_level? +

save_current_level 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.