Retrieve the list of existing objects in the current Max patch. Use this to understand the current state of the patch, including the objects(boxes) and patch cords(lines). The retrieved list contains a list of objects including their maxclass, varname for scripting, position(patching_rect), and t...
AI agents call get_objects_in_patch to retrieve information from MaxMSP-MCP-Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves data about the current Max patch state (objects, attributes, patch cords). It performs no modifications, does not execute code or commands, and has no destructive or financial implications. It is a straightforward Read operation with minimal risk.
From the tool's definition Tool description states 'Retrieve the list of existing objects' and 'understand the current state of the patch' — purely informational operations with no modification or execution capabilities. Returns object metadata and patch structure without side effects.
Documented attack patterns abuse exactly the kind of access get_objects_in_patch gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MaxMSP-MCP-Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_objects_in_patch:
{
"version": "1",
"default": "deny",
"tools": {
"get_objects_in_patch": {}
}
}get_objects_in_patch 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.
Retrieve the list of existing objects in the current Max patch. Use this to understand the current state of the patch, including the objects(boxes) and patch cords(lines). The retrieved list contains a list of objects including their maxclass, varname for scripting, position(patching_rect), and the boxtext when available, as well as a list of patch cords with their source and destination information. Returns: list: A list of objects and patch cords. It is categorised as a Read tool in the MaxMSP-MCP-Server MCP Server, which means it retrieves data without modifying state.
Register the MaxMSP-MCP-Server MCP server in PolicyLayer and add a rule for get_objects_in_patch: 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 MaxMSP-MCP-Server. Nothing to install.
get_objects_in_patch 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_objects_in_patch 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_objects_in_patch. 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_objects_in_patch is provided by the MaxMSP-MCP-Server MCP server (tiianhk/maxmsp-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 15 MaxMSP-MCP-Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
15 MaxMSP-MCP-Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.