dr_get_rollup
Aggregate stats: counts by grade (A+/A/B/C/D/F/X), by network, and by routed action. Defaults to last 500 rows; pass account_id to scope. Includes counts of conversion sends per network when available.
This record as markdown: /tools/io-github-0nork-0nmcp/dr-get-rollup.md
What dr_get_rollup does on 0nmcp
AI agents call dr_get_rollup to retrieve information from 0nmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why dr_get_rollup is rated Low
Even though dr_get_rollup only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs dr_get_rollup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0nmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dr_get_rollup, this is the rule to start with:
dr_get_rollup 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 0nmcp, apply this rule, and every dr_get_rollup call is checked against it from then on.
Questions about dr_get_rollup
Aggregate stats: counts by grade (A+/A/B/C/D/F/X), by network, and by routed action. Defaults to last 500 rows; pass account_id to scope. Includes counts of conversion sends per network when available. It is categorised as a Read tool in the 0nmcp MCP Server, which means it retrieves data without modifying state.
Register the 0n MCP server in PolicyLayer and add a rule for dr_get_rollup: 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 0nmcp. Nothing to install.
dr_get_rollup 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 dr_get_rollup 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 dr_get_rollup. 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.
dr_get_rollup is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0n, and thousands of servers like it.
This server
Across the catalogue