getThreadStats
Get aggregate statistics about the narrative engine: total threads, events, posts, disputes, and activity over time.
This record as markdown: /tools/io-github-homenshum-nodebench/getthreadstats.md
What getThreadStats does on Nodebench
AI agents call getThreadStats 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.
Why getThreadStats is rated Low
This tool only queries and returns statistical information with no side effects. It does not create, modify, delete, or execute operations—it simply reads and aggregates existing data about narrative engine metrics. This is a straightforward Read operation with minimal security risk.
From the tool's definition Tool description states it retrieves "aggregate statistics about the narrative engine: total threads, events, posts, disputes, and activity over time." The verb "Get" and focus on retrieving statistics with no mention of modification, deletion, or execution…
Attacks that exploit this kind of access
The rule that runs getThreadStats 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 getThreadStats, this is the rule to start with:
getThreadStats 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 Nodebench, apply this rule, and every getThreadStats call is checked against it from then on.
Questions about getThreadStats
Get aggregate statistics about the narrative engine: total threads, events, posts, disputes, and activity over time. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for getThreadStats: 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.
getThreadStats 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 getThreadStats 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 getThreadStats. 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.
getThreadStats 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.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue