Edit the code in an existing Python script component.
AI agents use edit_gh_script_component to create or update resources in GH_mcp_server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GH_mcp_server environment.
The tool modifies (edits) Python script component code, which is a reversible change to data. This is categorized as Write rather than Execute because the tool itself performs the edit operation rather than executing arbitrary code—execution would occur when the modified component runs. However, since edited code could have significant downstream effects on 3D models and design workflows, severity is rated medium.
From the tool's definition Tool name 'edit_gh_script_component' and description 'Edit the code in an existing Python script component' indicate modification of existing code/data within Grasshopper.
Documented attack patterns abuse exactly the kind of access edit_gh_script_component gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GH_mcp_server, and nothing reaches the server without passing your rules. This is the rule we recommend for edit_gh_script_component:
{
"version": "1",
"default": "deny",
"tools": {
"edit_gh_script_component": {
"limits": [
{
"counter": "edit_gh_script_component_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}edit_gh_script_component 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.
Free to start. No card required.
Edit the code in an existing Python script component. It is categorised as a Write tool in the GH_mcp_server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GH_mcp_server MCP server in PolicyLayer and add a rule for edit_gh_script_component: 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 GH_mcp_server. Nothing to install.
edit_gh_script_component 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 edit_gh_script_component 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 edit_gh_script_component. 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.
edit_gh_script_component is provided by the GH_mcp_server MCP server (veoery/gh_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 GH_mcp_server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 GH_mcp_server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.