AI agents use set_object_name to create or update resources in GOLEM-3DMCP-Rhino- — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GOLEM-3DMCP-Rhino- environment.
This is a Write operation because it creates or modifies data reversibly. Assigning names to objects is a non-destructive modification that can be easily undone or overwritten. It has minimal blast radius—worst case being confusion from poor naming conventions. It does not delete data (Destructive), execute code (Execute), trigger financial transactions (Financial), or read-only access (Read).
From the tool's definition The tool performs 'Assign a name to a Rhino object', which modifies metadata of an existing object. Naming is a reversible operation that changes object properties without affecting geometry, data integrity, or triggering external side effects.
Documented attack patterns abuse exactly the kind of access set_object_name gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GOLEM-3DMCP-Rhino-, and nothing reaches the server without passing your rules. This is the rule we recommend for set_object_name:
{
"version": "1",
"default": "deny",
"tools": {
"set_object_name": {
"limits": [
{
"counter": "set_object_name_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_object_name 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.
Assign a name to a Rhino object. It is categorised as a Write tool in the GOLEM-3DMCP-Rhino- MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GOLEM-3DMCP-Rhino- MCP server in PolicyLayer and add a rule for set_object_name: 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 GOLEM-3DMCP-Rhino-. Nothing to install.
set_object_name 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 set_object_name 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 set_object_name. 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.
set_object_name is provided by the GOLEM-3DMCP-Rhino- MCP server (thekinghippopotamus/golem-3dmcp-rhino-). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GOLEM-3DMCP-Rhino-, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
89 GOLEM-3DMCP-Rhino- tools catalogued and risk-classified — across an index of 43,000+ MCP servers.