get_narrative_status
Get narrative thread status from local SQLite. Returns threads grouped by phase (emerging, escalating, climax, resolution, dormant) with event counts. No network needed.
This record as markdown: /tools/io-github-homenshum-nodebench/get-narrative-status.md
What get_narrative_status does on Nodebench
AI agents call get_narrative_status 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 get_narrative_status is rated Low
This tool retrieves and queries narrative thread metadata from a local database without modifying, executing external operations, or deleting data. It is a pure read operation with minimal blast radius—misuse would only expose existing data structure information, not cause system damage or data loss.
From the tool's definition Tool description states 'Get narrative thread status from local SQLite' and 'Returns threads grouped by phase' with event counts. The verb 'Get' and 'Returns' indicate data retrieval only.
Attacks that exploit this kind of access
The rule that runs get_narrative_status 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_narrative_status, this is the rule to start with:
get_narrative_status 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 get_narrative_status call is checked against it from then on.
Questions about get_narrative_status
Get narrative thread status from local SQLite. Returns threads grouped by phase (emerging, escalating, climax, resolution, dormant) with event counts. No network needed. 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 get_narrative_status: 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.
get_narrative_status 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_narrative_status 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_narrative_status. 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_narrative_status 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