AI agents call list_objects 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.
list_objects retrieves or queries existing objects in the Rhino model without creating, modifying, or deleting data. Although the description is empty, the name and context clearly indicate this is a non-destructive read operation. The low severity reflects minimal risk if misused by an AI agent—listing objects causes no harm.
From the tool's definition Tool name 'list_objects' indicates a query/retrieval operation typical of Read category actions (list, get, fetch).
Documented attack patterns abuse exactly the kind of access list_objects 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 list_objects:
{
"version": "1",
"default": "deny",
"tools": {
"list_objects": {}
}
}list_objects 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.
list_objects. 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 list_objects: 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.
list_objects 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 list_objects 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 list_objects. 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.
list_objects 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.