Get detailed information about a specific object in the Maya scene.
AI agents call get_object_info to retrieve information from Maya 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 read-only query operation that retrieves scene data without side effects. It does not create, modify, delete, or execute any operations—it only fetches and returns information about existing objects. This aligns with the Read category definition: 'retrieves or queries data; no side effects'.
From the tool's definition Tool name is 'get_object_info' and description states it retrieves 'detailed information about a specific object in the Maya scene' with no modification, deletion, or execution capability mentioned.
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 Maya 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 Maya scene. It is categorised as a Read tool in the Maya MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Maya 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 Maya 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 Maya MCP Server MCP server (jeffreytsai1004/maya-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Maya MCP Server, 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.
10 Maya MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.