AI agents use add_max_object 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 tool creates new objects in Max patches, which is a reversible modification operation. While the description is empty (lowering confidence slightly), the name and context of sibling tools clearly indicate object creation capability. This falls under Write category as it adds/creates data structures within patches that can be undone (objects can be removed).
From the tool's definition Tool name 'add_max_object' indicates creation of objects within Max patches. Sibling tools include 'remove_max_object', 'connect_max_objects', 'disconnect_max_objects', and 'send_bang_to_object', establishing a pattern of patch manipulation.
Documented attack patterns abuse exactly the kind of access add_max_object 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 add_max_object:
{
"version": "1",
"default": "deny",
"tools": {
"add_max_object": {
"limits": [
{
"counter": "add_max_object_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_max_object 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.
add_max_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 add_max_object: 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.
add_max_object 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 add_max_object 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 add_max_object. 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.
add_max_object 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.