get_engine_context_health
Returns accumulated knowledge health: learnings count + freshness, conformance trend direction (improving/stable/regressing), recent run scores, content archive size, and workflow coverage. Use to understand how much context the engine has built up over time.
This record as markdown: /tools/io-github-homenshum-nodebench/get-engine-context-health.md
What get_engine_context_health does on Nodebench
AI agents call get_engine_context_health 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_engine_context_health is rated Low
This tool retrieves and queries accumulated knowledge metrics and context health status without side effects. It is purely informational, allowing users to understand engine state and historical performance. No data is modified, deleted, or executed. This is a straightforward Read operation with low security risk.
From the tool's definition Tool description states it 'Returns' health metrics including learnings count, freshness, conformance trends, run scores, and archive size. No creation, modification, deletion, execution, or financial operations are described.
Attacks that exploit this kind of access
The rule that runs get_engine_context_health 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_engine_context_health, this is the rule to start with:
get_engine_context_health 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_engine_context_health call is checked against it from then on.
Questions about get_engine_context_health
Returns accumulated knowledge health: learnings count + freshness, conformance trend direction (improving/stable/regressing), recent run scores, content archive size, and workflow coverage. Use to understand how much context the engine has built up 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 get_engine_context_health: 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_engine_context_health 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_engine_context_health 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_engine_context_health. 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_engine_context_health 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