rhino_schedule_by_layer

Aggregate objects per layer with optional filter and sublayer merging.

SERVERRhino SOURCEeasehee/rhino-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/easehee-rhino-mcp/rhino-schedule-by-layer.md

WHAT IT DOES

What rhino_schedule_by_layer does on Rhino

AI agents call rhino_schedule_by_layer to retrieve information from Rhino without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why rhino_schedule_by_layer is rated Low

The tool aggregates/collects objects organized by layer, which is a read/query operation that retrieves and summarizes data. There is no indication of modification, deletion, or execution of commands. 'Aggregate' and 'filter' are read semantics with no side effects.

From the tool's definition Aggregate objects per layer with optional filter and sublayer merging

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs rhino_schedule_by_layer safely

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

rhino_schedule_by_layer Allowed

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

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

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

FAQ

Questions about rhino_schedule_by_layer

What does the rhino_schedule_by_layer tool do? +

Aggregate objects per layer with optional filter and sublayer merging. It is categorised as a Read tool in the Rhino MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on rhino_schedule_by_layer? +

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

What risk level is rhino_schedule_by_layer? +

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

Can I rate-limit rhino_schedule_by_layer? +

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

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

rhino_schedule_by_layer is provided by the Rhino MCP server (easehee/rhino-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Rhino, and thousands of servers like it.

This server

All 245 Rhino tools →

Across the catalogue

aiva_get_delivery_schedule on AIVA MCP Server → The MCP Attack Database →

Guides

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