get_metrics
Read-only snapshot: feature/bug counts by status, completions by date, and velocity from the work log (tokens, additions/deletions, active days, recent tokens, and $ cost by model — see project config \
This record as markdown: /tools/ai-featureboard-featureboard/get-metrics.md
What get_metrics does on FeatureBoard
AI agents call get_metrics 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.
Why get_metrics is rated Low
This tool only retrieves and queries aggregated project metrics and statistics. It has no write, destructive, or side-effect capabilities. The explicit 'read-only' designation and passive data retrieval nature (counts, dates, logs) clearly place it in the Read category with low severity since an AI agent misusing it would only access existing metrics data without damaging or modifying anything.
From the tool's definition Tool name is 'get_metrics' and description explicitly states 'Read-only snapshot' that retrieves feature/bug counts, completion metrics, velocity data, and work log statistics without modification.
Attacks that exploit this kind of access
The rule that runs get_metrics 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 get_metrics, this is the rule to start with:
get_metrics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every get_metrics call is checked against it from then on.
Questions about get_metrics
Read-only snapshot: feature/bug counts by status, completions by date, and velocity from the work log (tokens, additions/deletions, active days, recent tokens, and $ cost by model — see project config \. It is categorised as a Read tool in the FeatureBoard MCP Server, which means it retrieves data without modifying state.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for get_metrics: 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.
get_metrics is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_metrics 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 get_metrics. 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.
get_metrics 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.
More on FeatureBoard, and thousands of servers like it.
This server
Across the catalogue