reporting_get_data
Get time-series reporting data for one or more graphs (CPU, memory, disk, network, etc.). Use reporting_graphs first to discover available graph names and identifiers.
This record as markdown: /tools/nasbridge/reporting-get-data.md
What reporting_get_data does on Nasbridge
AI agents call reporting_get_data to retrieve information from Nasbridge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why reporting_get_data is rated Low
This tool retrieves historical system performance metrics and monitoring data. It is a read-only query operation that does not modify, execute, delete, or commit any financial transactions. The data retrieved is informational and used for analysis/monitoring purposes only. The blast radius of misuse is minimal—an attacker could gather system performance information but cannot affect system state or operations.
From the tool's definition Tool description states 'Get time-series reporting data' which is a retrieval operation for metrics (CPU, memory, disk, network usage). The verb 'Get' and the context of querying existing graph data indicates no modifications, deletions, or side effects.
Attacks that exploit this kind of access
The rule that runs reporting_get_data safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reporting_get_data, this is the rule to start with:
reporting_get_data 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 Nasbridge, apply this rule, and every reporting_get_data call is checked against it from then on.
Questions about reporting_get_data
Get time-series reporting data for one or more graphs (CPU, memory, disk, network, etc.). Use reporting_graphs first to discover available graph names and identifiers. It is categorised as a Read tool in the Nasbridge MCP Server, which means it retrieves data without modifying state.
Register the Nasbridge MCP server in PolicyLayer and add a rule for reporting_get_data: 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 Nasbridge. Nothing to install.
reporting_get_data 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_get_data 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_get_data. 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_get_data is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nasbridge, and thousands of servers like it.
This server
Across the catalogue