AI agents use create_parametric_definition 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 name implies creation of a new artifact (a parametric definition), which maps to the Write category. However, the description is empty, so confidence is low. Given the server context (Rhino/Grasshopper modeling), this likely creates or writes a new parametric definition file or object. No indication of destructive, financial, or execution behavior from the name alone.
From the tool's definition Tool name 'create_parametric_definition' and empty description; name suggests creating a new parametric definition in Grasshopper/Rhino.
Documented attack patterns abuse exactly the kind of access create_parametric_definition 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 create_parametric_definition:
{
"version": "1",
"default": "deny",
"tools": {
"create_parametric_definition": {
"limits": [
{
"counter": "create_parametric_definition_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_parametric_definition 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.
create_parametric_definition. 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 create_parametric_definition: 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.
create_parametric_definition 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 create_parametric_definition 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 create_parametric_definition. 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.
create_parametric_definition 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.