Retrieve detailed flows data from the ntopng flows database.
AI agents call query_ntopng_flows_data 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 queries network flow data from ntopng's database for monitoring and analysis purposes. It performs a retrieval operation without modifying, deleting, or executing code. The sibling tools (fetch_*, get_*) all confirm this server provides read-only network monitoring data access.
From the tool's definition Tool name 'query_ntopng_flows_data' and description 'Retrieve detailed flows data from the ntopng flows database' indicate a retrieval operation with no side effects. The verb 'Retrieve' and context of querying a monitoring database confirm read-only access.
Attacks that exploit this kind of access
Retrieve detailed flows data from the ntopng flows database. 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 query_ntopng_flows_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 Mcp Ntopng. Nothing to install.
query_ntopng_flows_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 query_ntopng_flows_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 query_ntopng_flows_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.
query_ntopng_flows_data 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 →