estimate_work

Per-ticket token estimates for all open tickets, derived from the board

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/estimate-work.md

WHAT IT DOES

What estimate_work does on FeatureBoard

AI agents call estimate_work 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 estimate_work is rated Low

The tool retrieves and computes estimates from existing board data (open tickets), which is a read/query operation. It derives information from the board without creating, modifying, or deleting anything. Severity is low as misuse would only expose project planning data.

From the tool's definition 'token estimates for all open tickets, derived from the board' — this reads/queries existing ticket data to produce estimates, with no indication of side effects

Attacks that exploit this kind of access

RECOMMENDED RULE

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

estimate_work Allowed

estimate_work 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": {
    "estimate_work": {}
  }
}

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 estimate_work call is checked against it from then on.

FAQ

Questions about estimate_work

What does the estimate_work tool do? +

Per-ticket token estimates for all open tickets, derived from the board. 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 estimate_work? +

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

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

Can I rate-limit estimate_work? +

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

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

estimate_work 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

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