list_decisions

Read a project

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

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-featureboard-featureboard/list-decisions.md

WHAT IT DOES

What list_decisions does on FeatureBoard

AI agents call list_decisions to retrieve information from FeatureBoard without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_decisions is rated Low

This tool retrieves or queries decision data from a project board without creating, modifying, or deleting any information. It is a straightforward read operation with minimal blast radius if misused by an AI agent—worst case being unauthorized information disclosure of non-sensitive project decisions.

From the tool's definition Tool name is 'list_decisions' and description states 'Read a project'. The verb 'Read' explicitly indicates data retrieval with no side effects. No modification, deletion, or execution capability is implied.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_decisions Allowed

list_decisions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_decisions": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about list_decisions

What does the list_decisions tool do? +

Read a project. It is categorised as a Read tool in the FeatureBoard MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_decisions? +

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

list_decisions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_decisions? +

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

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

list_decisions 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

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →