get_monthly_report

Monthly rollup of actions: weekly breakdown, trending categories, velocity (actions/day), milestone timeline.

SERVERNodebench SOURCEnodebench-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-homenshum-nodebench/get-monthly-report.md

WHAT IT DOES

What get_monthly_report does on Nodebench

AI agents call get_monthly_report to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_monthly_report is rated Low

This tool retrieves and aggregates historical data (actions, trends, velocity metrics) into a report. It performs no mutations, deletions, external execution, or financial operations. The verb 'rollup' and 'breakdown' indicate query and summarization only, making it a straightforward Read category tool.

From the tool's definition Tool description states it provides 'Monthly rollup of actions: weekly breakdown, trending categories, velocity (actions/day), milestone timeline' — these are all data retrieval and summarization operations with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_monthly_report safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_monthly_report, this is the rule to start with:

get_monthly_report Allowed

get_monthly_report is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_monthly_report": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Nodebench, apply this rule, and every get_monthly_report call is checked against it from then on.

FAQ

Questions about get_monthly_report

What does the get_monthly_report tool do? +

Monthly rollup of actions: weekly breakdown, trending categories, velocity (actions/day), milestone timeline. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_monthly_report? +

Register the Nodebench MCP server in PolicyLayer and add a rule for get_monthly_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 Nodebench. Nothing to install.

What risk level is get_monthly_report? +

get_monthly_report is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_monthly_report? +

Yes. Add a rate_limit block to the get_monthly_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.

How do I block get_monthly_report completely? +

Set action: deny in the PolicyLayer policy for get_monthly_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.

What MCP server provides get_monthly_report? +

get_monthly_report is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →