batch_patch_ui_schema · Nocobase MCP: Risk & Policy

WHAT IT DOES

What batch_patch_ui_schema does on Nocobase

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

WHY IT NEEDS A POLICY

Why batch_patch_ui_schema needs a policy

The 'batch_patch_ui_schema' tool creates or modifies UI schema data in bulk. Patching is a reversible write operation (not delete/drop). The batch nature and potential to affect multiple UI schema nodes simultaneously raises the severity to 'high' due to blast radius, but it remains in the Write category since patches are typically reversible and do not constitute destructive or irreversible changes.

From the tool's definition Tool name contains 'patch' and description states it modifies 'multiple UI schema nodes in a single request', which is a reversible modification operation affecting multiple entities at once.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_patch_ui_schema Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "batch_patch_ui_schema": {
      "limits": [
        {
          "counter": "batch_patch_ui_schema_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Nocobase, so you can run agents against it safely.

FAQ

Questions about batch_patch_ui_schema

What does the batch_patch_ui_schema tool do? +

Patch multiple UI schema nodes in a single request. Each object in the patches array must include. It is categorised as a Write tool in the Nocobase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on batch_patch_ui_schema? +

Register the Nocobase MCP server in PolicyLayer and add a rule for batch_patch_ui_schema: 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 Nocobase. Nothing to install.

What risk level is batch_patch_ui_schema? +

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

Can I rate-limit batch_patch_ui_schema? +

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

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

batch_patch_ui_schema is provided by the Nocobase MCP server (puguhsudarma/nocobase-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.