Disconnect two Max objects. Args: src_varname (str): Variable name of the source object. outlet_idx (int): Outlet index on the source object. dst_varname (str): Variable name of the destination object. inlet_idx (int): Inlet index on the destination object.
AI agents use disconnect_max_objects to create or update resources in MaxMSP-MCP-Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MaxMSP-MCP-Server environment.
This operation creates or modifies patch data in a reversible manner—removing a connection from a Max patch is comparable to an 'update' or 'delete' operation on patch topology, not a destructive system-level action. The change can be undone by reconnecting the objects. While it modifies the patch structure, it does not destroy data irreversibly, execute external code, or affect the host system.
From the tool's definition The tool 'disconnect_max_objects' modifies patch connectivity by severing a connection between two Max objects. The parameters (src_varname, outlet_idx, dst_varname, inlet_idx) specify which connection to remove.
Documented attack patterns abuse exactly the kind of access disconnect_max_objects 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 disconnect_max_objects:
{
"version": "1",
"default": "deny",
"tools": {
"disconnect_max_objects": {
"limits": [
{
"counter": "disconnect_max_objects_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}disconnect_max_objects stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Disconnect two Max objects. Args: src_varname (str): Variable name of the source object. outlet_idx (int): Outlet index on the source object. dst_varname (str): Variable name of the destination object. inlet_idx (int): Inlet index on the destination object. It is categorised as a Write tool in the MaxMSP-MCP-Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MaxMSP-MCP-Server MCP server in PolicyLayer and add a rule for disconnect_max_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 MaxMSP-MCP-Server. Nothing to install.
disconnect_max_objects is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the disconnect_max_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 disconnect_max_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.
disconnect_max_objects 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.