Semantic wrapper over create_architecture_link: tie a task to one ArchitectureNode it will touch. Call this immediately after create_task when you know which workspace/module the task modifies. Populates the graph so that subsequent prepare_task_context calls receive richer execution context.
AI agents use link_task_to_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.
This tool creates links and modifies the architecture graph structure within RoadBoard, which is a Write operation—it creates relationships and updates project state reversibly. It does not delete, execute arbitrary code, or trigger external financial operations.
From the tool's definition The tool is a semantic wrapper over create_architecture_link that 'tie[s] a task to one ArchitectureNode' and 'Populates the graph'. These are modifications to project state (graph/linking structure).
Attacks that exploit this kind of access
Semantic wrapper over create_architecture_link: tie a task to one ArchitectureNode it will touch. Call this immediately after create_task when you know which workspace/module the task modifies. Populates the graph so that subsequent prepare_task_context calls receive richer execution context. 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.
Register the RoadBoard MCP server in PolicyLayer and add a rule for link_task_to_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.
link_task_to_node 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 link_task_to_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.
Set action: deny in the PolicyLayer policy for link_task_to_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.
link_task_to_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.
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 →