move_flow_model · Nocobase MCP: Risk & Policy

WHAT IT DOES

What move_flow_model does on Nocobase

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

The tool performs a repositioning operation that changes the state of flow models by altering their position in a hierarchy or sequence. This is a Write-category action because it modifies data structure reversibly (the move can be undone by moving to another position). It does not execute arbitrary code, delete data permanently, or trigger external operations.

From the tool's definition Tool description states 'Move a flowPage block/model to a different position' - this modifies the structural position/order of UI components, which is a reversible modification to data (the layout/arrangement) without permanent deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_flow_model Rate-limited

move_flow_model 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": {
    "move_flow_model": {
      "limits": [
        {
          "counter": "move_flow_model_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 move_flow_model

What does the move_flow_model tool do? +

Move a flowPage block/model to a different position relative to another block. 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 move_flow_model? +

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

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

Can I rate-limit move_flow_model? +

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

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

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