Show an activity and security report: tool call counts, blocks, DLP findings, agent cost,
AI agents call node9_report to retrieve information from Node9-Proxy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and presents audit/analytics data from the proxy layer. It has no side effects, creates no data, executes no commands, and does not alter system state. The blast radius of misuse is minimal — an agent could only over-expose metrics or logs, which is a confidentiality concern but not operationally destructive. Categorized as Read with low severity.
From the tool's definition Tool description states 'Show an activity and security report' — language indicating retrieval and display of existing log/metric data (tool call counts, blocks, DLP findings, agent cost). No mutation, deletion, or execution of external operations implied.
Documented attack patterns abuse exactly the kind of access node9_report gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Node9-Proxy, and nothing reaches the server without passing your rules. This is the rule we recommend for node9_report:
{
"version": "1",
"default": "deny",
"tools": {
"node9_report": {}
}
}node9_report 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.
Show an activity and security report: tool call counts, blocks, DLP findings, agent cost,. It is categorised as a Read tool in the Node9-Proxy MCP Server, which means it retrieves data without modifying state.
Register the Node9-Proxy MCP server in PolicyLayer and add a rule for node9_report: 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 Node9-Proxy. Nothing to install.
node9_report 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 node9_report 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 node9_report. 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.
node9_report is provided by the Node9-Proxy MCP server (node9-ai/node9-proxy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 Node9-Proxy tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 Node9-Proxy tools catalogued and risk-classified — across an index of 42,500+ MCP servers.