gh_get_parameter
Read the current value of a component parameter.
This record as markdown: /tools/easehee-rhino-mcp/gh-get-parameter.md
What gh_get_parameter does on Rhino
AI agents call gh_get_parameter 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 gh_get_parameter is rated Low
This tool retrieves the current value of a parameter without modifying state, executing code, or triggering side effects. It is purely informational and poses minimal risk even if misused by an AI agent, as it cannot alter geometry, trigger operations, or cause harm.
From the tool's definition Tool name is 'gh_get_parameter' and description states 'Read the current value of a component parameter.' The verb 'read' and lack of any modification, execution, or destructive action clearly indicate this is a read-only retrieval operation.
Attacks that exploit this kind of access
The rule that runs gh_get_parameter 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 gh_get_parameter, this is the rule to start with:
gh_get_parameter 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 gh_get_parameter call is checked against it from then on.
Questions about gh_get_parameter
Read the current value of a component parameter. 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 gh_get_parameter: 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.
gh_get_parameter 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 gh_get_parameter 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 gh_get_parameter. 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.
gh_get_parameter 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