Get the current reporting/metrics configuration.
AI agents call reporting_config 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.
This tool retrieves configuration data about reporting and metrics without creating, modifying, or deleting any resources. It is a simple query operation that only reads existing configuration state, making it a Read category risk with low severity since configuration data exposure has minimal blast radius compared to operational changes.
From the tool's definition Tool name 'reporting_config' and description 'Get the current reporting/metrics configuration' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access reporting_config gives an agent:
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_config:
{
"version": "1",
"default": "deny",
"tools": {
"reporting_config": {}
}
}reporting_config is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the current reporting/metrics configuration. It is categorised as a Read tool in the Truenas MCP Server, which means it retrieves data without modifying state.
Register the Truenas MCP server in PolicyLayer and add a rule for reporting_config: 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.
reporting_config 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 reporting_config 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 reporting_config. 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.
reporting_config 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.
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.