reporting_config
Get the current reporting/metrics configuration.
This record as markdown: /tools/nasbridge/reporting-config.md
What reporting_config does on Nasbridge
AI agents call reporting_config 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_config is rated Low
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.
Attacks that exploit this kind of access
The rule that runs reporting_config 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_config, this is the rule to start with:
reporting_config 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_config call is checked against it from then on.
Questions about reporting_config
Get the current reporting/metrics configuration. 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_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 Nasbridge. 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 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