insert_adjacent_schema · Nocobase MCP: Risk & Policy

WHAT IT DOES

What insert_adjacent_schema does on Nocobase

AI agents use insert_adjacent_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 insert_adjacent_schema needs a policy

This tool creates new schema nodes and modifies the structural hierarchy of UI schemas by inserting them at various positions (sibling or child relationships). This is a reversible modification operation that does not permanently delete data or execute arbitrary code, placing it in the Write category.

From the tool's definition The tool 'insert_adjacent_schema' explicitly performs an insert operation that creates a schema node at a specified position relative to a target node, modifying the UI schema structure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

insert_adjacent_schema Rate-limited

insert_adjacent_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": {
    "insert_adjacent_schema": {
      "limits": [
        {
          "counter": "insert_adjacent_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 insert_adjacent_schema

What does the insert_adjacent_schema tool do? +

Insert a schema node at a position relative to a target node. Position values: beforeBegin (prev sibling), afterBegin (first child), beforeEnd (last child), afterEnd (next sibling). 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 insert_adjacent_schema? +

Register the Nocobase MCP server in PolicyLayer and add a rule for insert_adjacent_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 insert_adjacent_schema? +

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

Can I rate-limit insert_adjacent_schema? +

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

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

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