get_reboot_schedule

获取重启计划

SERVERIkuai SOURCEgxxHuang/ikuai-mcp-server

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/ikuai-mcp-server/get-reboot-schedule.md

WHAT IT DOES

What get_reboot_schedule does on Ikuai

AI agents call get_reboot_schedule to retrieve information from Ikuai 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_reboot_schedule is rated Low

This tool retrieves or queries reboot schedule configuration data without side effects. It does not execute reboots, modify schedules, or delete data. This is a read-only information retrieval operation on router configuration.

From the tool's definition Tool name 'get_reboot_schedule' and description '获取重启计划' (get reboot schedule) indicate retrieval of existing schedule data with no modification or execution of reboots.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_reboot_schedule safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ikuai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_reboot_schedule, this is the rule to start with:

get_reboot_schedule Allowed

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ikuai, apply this rule, and every get_reboot_schedule call is checked against it from then on.

FAQ

Questions about get_reboot_schedule

What does the get_reboot_schedule tool do? +

获取重启计划. It is categorised as a Read tool in the Ikuai MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_reboot_schedule? +

Register the Ikuai MCP server in PolicyLayer and add a rule for get_reboot_schedule: 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 Ikuai. Nothing to install.

What risk level is get_reboot_schedule? +

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

Can I rate-limit get_reboot_schedule? +

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

Set action: deny in the PolicyLayer policy for get_reboot_schedule. 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_reboot_schedule? +

get_reboot_schedule is provided by the Ikuai MCP server (gxxHuang/ikuai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ikuai, and thousands of servers like it.

This server

All 229 Ikuai tools →

Across the catalogue

aiva_get_delivery_schedule on AIVA MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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