retention_status

Check retention.sh connection status and QA metrics. Shows team code, QA score, member count, and last sync time. Use to verify retention.sh integration is working.

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/retention-status.md

WHAT IT DOES

What retention_status does on Nodebench

AI agents call retention_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.

RISK

Why retention_status is rated Low

The tool retrieves and displays status information and metrics from an existing integration. It performs queries and status checks without creating, modifying, deleting, or executing operations. The phrase 'Use to verify retention.sh integration is working' confirms its diagnostic/monitoring purpose rather than any operational capability.

From the tool's definition Tool description indicates it 'Check[s] retention.sh connection status and QA metrics' and 'Shows team code, QA score, member count, and last sync time.' These are all read-only information retrieval operations with no modification or execution of external…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs retention_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 retention_status, this is the rule to start with:

retention_status Allowed

retention_status 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": {
    "retention_status": {}
  }
}

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 retention_status call is checked against it from then on.

FAQ

Questions about retention_status

What does the retention_status tool do? +

Check retention.sh connection status and QA metrics. Shows team code, QA score, member count, and last sync time. Use to verify retention.sh integration is working. 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 retention_status? +

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

What risk level is retention_status? +

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

Can I rate-limit retention_status? +

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

How do I block retention_status completely? +

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

What MCP server provides retention_status? +

retention_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.

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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