create_architecture_annotation

WHAT IT DOES

What create_architecture_annotation does on RoadBoard

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

The tool creates new annotation data attached to existing architecture nodes, which is a reversible write operation. It modifies project state but does not execute code, delete data, or move money.

From the tool's definition Tool name 'create_architecture_annotation' and description 'Attach a free-text annotation to an ArchitectureNode' indicate creation and modification of project state data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_architecture_annotation Rate-limited

create_architecture_annotation 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_annotation": {
      "limits": [
        {
          "counter": "create_architecture_annotation_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_annotation

What does the create_architecture_annotation tool do? +

Attach a free-text annotation to an ArchitectureNode. Use for semantic context that cannot be derived from source (e.g. 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_annotation? +

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

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

Can I rate-limit create_architecture_annotation? +

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

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

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

// THE FULL RECORD

create_architecture_annotation is one line of RoadBoard's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →