get_autopilot_status

Check the status of scheduled tasks: when the last run happened,

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

WHAT IT DOES

What get_autopilot_status does on Nodebench

AI agents call get_autopilot_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 get_autopilot_status is rated Low

This tool retrieves status information about scheduled tasks without executing, modifying, or deleting anything. It is a read-only operation that queries the state of existing resources. No side effects or irreversible actions are possible.

From the tool's definition Tool name 'get_autopilot_status' and description 'Check the status of scheduled tasks: when the last run happened' indicate a query/retrieval operation with no modification or execution of tasks.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_autopilot_status Allowed

get_autopilot_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": {
    "get_autopilot_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 get_autopilot_status call is checked against it from then on.

FAQ

Questions about get_autopilot_status

What does the get_autopilot_status tool do? +

Check the status of scheduled tasks: when the last run happened,. 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 get_autopilot_status? +

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

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

Can I rate-limit get_autopilot_status? +

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

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

get_autopilot_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 →