AI agents use attach_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.
This tool creates or modifies data relationships in a reversible way (attaching a block to a parent). It does not execute arbitrary code, delete data, or perform financial operations. The action is reversible (can be detached), making it Write rather than Destructive.
From the tool's definition Tool description states 'Attach an existing flowPage block/model to a parent' and 'add an existing block into a flowPage container at a specific position.' These actions modify the structure and configuration of UI/flow models by creating new associations or…
Attacks that exploit this kind of access
Attach an existing flowPage block/model to a parent. Use this to add an existing block into a flowPage container at a specific position. 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.
Register the Nocobase MCP server in PolicyLayer and add a rule for attach_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.
attach_flow_model is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the attach_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.
Set action: deny in the PolicyLayer policy for attach_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.
attach_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →