Get detailed information about a specific object in the Blender scene. Parameters: - object_name: The name of the object to get information about
AI agents call get_object_info to retrieve information from Tripo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure information retrieval tool that queries Blender scene data. It retrieves object metadata without creating, modifying, deleting, or executing any operations. The blast radius is minimal—misuse would only expose existing scene information to the AI agent without enabling destructive or risky actions on the asset.
From the tool's definition Tool name is 'get_object_info' and description states 'Get detailed information about a specific object in the Blender scene.' The only parameter is 'object_name' for querying. No modification, deletion, execution, or side effects are described.
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 Tripo MCP Server, 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.
Get detailed information about a specific object in the Blender scene. Parameters: - object_name: The name of the object to get information about. It is categorised as a Read tool in the Tripo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tripo MCP Server 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 Tripo MCP Server. 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 Tripo MCP Server MCP server (vast-ai-research/tripo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 Tripo MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 Tripo MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.