Low Risk

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.

How to control reporting_graphs ↓

What reporting_graphs does on Truenas

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

Low Risk

Why reporting_graphs needs a policy

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.

Documented attack patterns abuse exactly the kind of access reporting_graphs gives an agent:

How to control reporting_graphs

PolicyLayer is an MCP gateway — it sits between your AI agents and Truenas, and nothing reaches the server without passing your rules. This is the rule we recommend for reporting_graphs:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "reporting_graphs": {}
  }
}

reporting_graphs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Truenas — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

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.

Enforce policy on every Truenas tool call.

Start from Truenas, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

279 Truenas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.