Retrieve statistics for all alerts.
AI agents call get_ntopng_all_alert_stats to retrieve information from Mcp Ntopng without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves alert statistics from ntopng network monitoring software. It queries existing data without creating, modifying, deleting, or executing operations. The blast radius of misuse is minimal: an unauthorized actor could view network alert metrics but cannot alter network state, delete data, or trigger actions.
From the tool's definition Tool name contains 'get_' and 'stats'; description states 'Retrieve statistics' — both indicate read-only data retrieval with no side effects. Sibling tools follow the same 'get_' and 'fetch_' pattern, confirming this server exposes monitoring queries.
Attacks that exploit this kind of access
Retrieve statistics for all alerts. It is categorised as a Read tool in the Mcp Ntopng MCP Server, which means it retrieves data without modifying state.
Register the Mcp Ntopng MCP server in PolicyLayer and add a rule for get_ntopng_all_alert_stats: 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 Mcp Ntopng. Nothing to install.
get_ntopng_all_alert_stats 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 get_ntopng_all_alert_stats 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 get_ntopng_all_alert_stats. 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.
get_ntopng_all_alert_stats is provided by the Mcp Ntopng MCP server (marcoeg/mcp-server-ntopng). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →