rhino_get_module_functions
Get all functions in a specific RhinoScript module with signatures.
This record as markdown: /tools/easehee-rhino-mcp/rhino-get-module-functions.md
What rhino_get_module_functions does on Rhino
AI agents call rhino_get_module_functions 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.
Why rhino_get_module_functions is rated Low
This tool queries and retrieves information about available functions and their signatures from a RhinoScript module. It performs no side effects, does not execute code, does not modify data, and is purely informational in nature. This is a classic Read category operation.
From the tool's definition Tool name 'rhino_get_module_functions' and description 'Get all functions in a specific RhinoScript module with signatures' indicate retrieval of metadata about available functions with no modification or execution of those functions.
Attacks that exploit this kind of access
The rule that runs rhino_get_module_functions 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_get_module_functions, this is the rule to start with:
rhino_get_module_functions is read-only, so it stays allowed. 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_get_module_functions call is checked against it from then on.
Questions about rhino_get_module_functions
Get all functions in a specific RhinoScript module with signatures. It is categorised as a Read tool in the Rhino MCP Server, which means it retrieves data without modifying state.
Register the Rhino MCP server in PolicyLayer and add a rule for rhino_get_module_functions: 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_get_module_functions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the rhino_get_module_functions 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_get_module_functions. 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_get_module_functions 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