Return full detail for a single Rhino object identified by its GUID.
AI agents call get_object_info to retrieve information from GOLEM-3DMCP-Rhino- without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries information about a 3D object in Rhino by its unique identifier. It performs no creation, modification, deletion, or execution of code. The operation is read-only and returns data without altering the model state. Severity is low because retrieving object properties poses minimal risk—an agent cannot cause structural damage, financial harm, or irreversible changes through this query.
From the tool's definition Tool name 'get_object_info' and description 'Return full detail for a single Rhino object identified by its GUID' indicates retrieval of object metadata with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_object_info 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 get_object_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_object_info": {}
}
}get_object_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Return full detail for a single Rhino object identified by its GUID. It is categorised as a Read tool in the GOLEM-3DMCP-Rhino- MCP Server, which means it retrieves data without modifying state.
Register the GOLEM-3DMCP-Rhino- MCP server in PolicyLayer and add a rule for get_object_info: 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.
get_object_info 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 get_object_info 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 get_object_info. 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.
get_object_info 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.