retention_get_status

Return the latest retention.sh connection and recent event history from local MCP state.

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-get-status.md

WHAT IT DOES

What retention_get_status does on Nodebench

AI agents call retention_get_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_get_status is rated Low

This tool retrieves and returns status information and event history. It performs a query operation ('Return') on local state without creating, modifying, deleting, or executing any operations. The data retrieved is informational only, making this a Read category tool with low severity.

From the tool's definition Tool description states 'Return the latest retention.sh connection and recent event history from local MCP state.' The verb 'Return' and retrieval of status/history indicate a read-only operation that queries existing data without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

retention_get_status Allowed

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

FAQ

Questions about retention_get_status

What does the retention_get_status tool do? +

Return the latest retention.sh connection and recent event history from local MCP state. 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_get_status? +

Register the Nodebench MCP server in PolicyLayer and add a rule for retention_get_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_get_status? +

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

Can I rate-limit retention_get_status? +

Yes. Add a rate_limit block to the retention_get_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_get_status completely? +

Set action: deny in the PolicyLayer policy for retention_get_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_get_status? +

retention_get_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

get_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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