AI agents call list_objects to retrieve information from GH_mcp_server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query-like operation that retrieves and displays information about objects within a 3D model file. There is no data modification, deletion, code execution, or financial impact. The blast radius of misuse is minimal—an AI agent could at worst retrieve sensitive design information, but cannot alter the file or trigger external operations.
From the tool's definition Tool name is 'list_objects' and description states it 'List[s] all objects in a Rhino file' - a pure retrieval operation with no modification or side effects.
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 GH_mcp_server, 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 all objects in a Rhino file. It is categorised as a Read tool in the GH_mcp_server MCP Server, which means it retrieves data without modifying state.
Register the GH_mcp_server 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 GH_mcp_server. 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 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.