reporting_graphs

List all available reporting graphs (CPU, memory, disk, network, etc.). Use the graph names with reporting_get_data to fetch time-series data.

SERVERTruenas SOURCEspranab/truenas-mcp

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/spranab-truenas-mcp/reporting-graphs.md

WHAT IT DOES

What reporting_graphs does on Truenas

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

RISK

Why reporting_graphs is rated Low

This is a read-only query operation that retrieves configuration/metadata about available reporting graphs without modifying, executing, or deleting anything. The blast radius is minimal—an AI agent cannot cause harm by listing available graph names. It serves as a discovery mechanism for the reporting_get_data tool.

From the tool's definition Tool description states "List all available reporting graphs" with no side effects. Returns metadata about available graphs for use with a separate data-fetching tool.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs reporting_graphs safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Truenas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reporting_graphs, this is the rule to start with:

reporting_graphs Allowed

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

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

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

FAQ

Questions about reporting_graphs

What does the reporting_graphs tool do? +

List all available reporting graphs (CPU, memory, disk, network, etc.). Use the graph names with reporting_get_data to fetch time-series data. It is categorised as a Read tool in the Truenas MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on reporting_graphs? +

Register the Truenas MCP server in PolicyLayer and add a rule for reporting_graphs: 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 Truenas. Nothing to install.

What risk level is reporting_graphs? +

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

Can I rate-limit reporting_graphs? +

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

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

reporting_graphs is provided by the Truenas MCP server (spranab/truenas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Truenas, and thousands of servers like it.

This server

All 279 Truenas tools →

Across the catalogue

The MCP Attack Database →

Guides

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