create_architecture_node · RoadBoard MCP: Risk & Policy

WHAT IT DOES

What create_architecture_node does on RoadBoard

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

WHY IT NEEDS A POLICY

Why create_architecture_node needs a policy

This tool creates new architectural nodes (workspaces/modules/services) in a project graph. Creation is a write operation that modifies project state reversibly — nodes can be updated or removed without permanent loss. The blast radius is medium: misconfiguration could clutter the architecture graph or create incorrect module structures, but this would be correctable through subsequent modifications.

From the tool's definition Tool name is 'create_architecture_node' and description states 'Create an ArchitectureNode' — the verb 'create' indicates data creation. Description further specifies it adds nodes to 'the project graph', which is a reversible structural modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_architecture_node Rate-limited

create_architecture_node 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": {
    "create_architecture_node": {
      "limits": [
        {
          "counter": "create_architecture_node_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 RoadBoard, so you can run agents against it safely.

FAQ

Questions about create_architecture_node

What does the create_architecture_node tool do? +

Create an ArchitectureNode (workspace/module/service) in the project graph. Call once per workspace while parsing package.json. Requires a repositoryId from create_architecture_repository. It is categorised as a Write tool in the RoadBoard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_architecture_node? +

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

What risk level is create_architecture_node? +

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

Can I rate-limit create_architecture_node? +

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

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

create_architecture_node is provided by the RoadBoard MCP server (maless88/roadboard). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.