Retrieve statistics for flow alerts.
AI agents call get_ntopng_flow_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, a network monitoring platform. It performs no data modification, deletion, or execution of external actions. It is a straightforward read operation that queries monitoring data, similar to its sibling tools which all retrieve or fetch various network statistics.
From the tool's definition Tool description states 'Retrieve statistics for flow alerts.' The verb 'Retrieve' indicates data fetching without modification. All sibling tools use verbs like 'fetch,' 'get,' and 'Retrieve,' consistently indicating read-only operations.
Attacks that exploit this kind of access
Retrieve statistics for flow 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_flow_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_flow_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_flow_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_flow_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_flow_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 →