export_metrics

Flat-file export of analytics for external BI/spreadsheet use, mirroring export_tasks: what:

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/export-metrics.md

WHAT IT DOES

What export_metrics does on FeatureBoard

AI agents call export_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.

RISK

Why export_metrics is rated Low

The tool exports analytics data to a flat file for BI/spreadsheet consumption. This is a read operation — it retrieves and serializes existing metrics without creating, modifying, or deleting any data. No side effects are implied beyond generating an export file. Severity is low because misuse would only expose analytics data.

From the tool's definition 'Flat-file export of analytics' and 'mirroring export_tasks' indicate read-only data retrieval/export for external use

Attacks that exploit this kind of access

RECOMMENDED RULE

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

export_metrics Allowed

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

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

FAQ

Questions about export_metrics

What does the export_metrics tool do? +

Flat-file export of analytics for external BI/spreadsheet use, mirroring export_tasks: what:. 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 export_metrics? +

Register the FeatureBoard MCP server in PolicyLayer and add a rule for export_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.

What risk level is export_metrics? +

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

Can I rate-limit export_metrics? +

Yes. Add a rate_limit block to the export_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.

How do I block export_metrics completely? +

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

What MCP server provides export_metrics? +

export_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.

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 →