rhino_schedule_export_csv
Write rows produced by any rhino_schedule_* tool to CSV.
This record as markdown: /tools/easehee-rhino-mcp/rhino-schedule-export-csv.md
What rhino_schedule_export_csv does on Rhino
AI agents use rhino_schedule_export_csv to create or update resources in Rhino, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rhino environment.
Why rhino_schedule_export_csv is rated Medium
This tool creates or modifies a CSV file by exporting schedule data. It is reversible (the file can be deleted or overwritten) and has no destructive, financial, or code execution components. While it produces a file, it does not execute arbitrary code or scripts. The 'Write' category is most appropriate as it represents data creation/modification.
From the tool's definition Tool description states 'Write rows produced by any rhino_schedule_* tool to CSV', using the explicit action verb 'Write' and indicating creation/modification of a CSV file as an output artifact.
Attacks that exploit this kind of access
The rule that runs rhino_schedule_export_csv 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_export_csv, this is the rule to start with:
rhino_schedule_export_csv stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Rhino, apply this rule, and every rhino_schedule_export_csv call is checked against it from then on.
Questions about rhino_schedule_export_csv
Write rows produced by any rhino_schedule_* tool to CSV. It is categorised as a Write tool in the Rhino MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rhino MCP server in PolicyLayer and add a rule for rhino_schedule_export_csv: 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.
rhino_schedule_export_csv is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the rhino_schedule_export_csv 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.
Set action: deny in the PolicyLayer policy for rhino_schedule_export_csv. 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.
rhino_schedule_export_csv 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.
More on Rhino, and thousands of servers like it.
This server
Across the catalogue