check_acceptance

Toggle the checkbox on acceptance criterion #index (1-based) of a ticket

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/check-acceptance.md

WHAT IT DOES

What check_acceptance does on FeatureBoard

AI agents use check_acceptance 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 check_acceptance is rated Medium

This tool modifies the state of an acceptance criterion checkbox on a ticket (toggling it on/off). It creates a reversible change to existing data, fitting the Write category. Misuse could cause acceptance criteria to be incorrectly marked as met or unmet, potentially allowing incomplete work to be shipped, hence medium severity.

From the tool's definition Toggle the checkbox on acceptance criterion #index (1-based) of a ticket

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_acceptance 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 check_acceptance, this is the rule to start with:

check_acceptance Rate-limited

check_acceptance 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": {
    "check_acceptance": {
      "limits": [
        {
          "counter": "check_acceptance_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 check_acceptance call is checked against it from then on.

FAQ

Questions about check_acceptance

What does the check_acceptance tool do? +

Toggle the checkbox on acceptance criterion #index (1-based) of a ticket. 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 check_acceptance? +

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

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

Can I rate-limit check_acceptance? +

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

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

check_acceptance 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 →