link_tasks

Relate two tickets. kind \

SERVERFeatureBoard SOURCEhttps://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-featureboard-featureboard/link-tasks.md

WHAT IT DOES

What link_tasks does on FeatureBoard

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

RISK

Why link_tasks is rated Medium

Linking tasks is a reversible modification that establishes metadata relationships between existing tickets. It is not destructive (no deletion), not financial, and not execute-class (no code execution or external operations triggered). It falls squarely into Write: creating relational data.

From the tool's definition Tool name is 'link_tasks' and description states 'Relate two tickets' — this creates a relationship/association between existing tickets without modifying their core content or deleting anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs link_tasks safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For link_tasks, this is the rule to start with:

link_tasks Rate-limited

link_tasks 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": {
    "link_tasks": {
      "limits": [
        {
          "counter": "link_tasks_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every link_tasks call is checked against it from then on.

FAQ

Questions about link_tasks

What does the link_tasks tool do? +

Relate two tickets. kind \. It is categorised as a Write tool in the FeatureBoard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on link_tasks? +

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

What risk level is link_tasks? +

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

Can I rate-limit link_tasks? +

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

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

link_tasks is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FeatureBoard, and thousands of servers like it.

This server

All 215 FeatureBoard tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →