Set the value of a object in MaxMSP. The object can be a number box, a slider, a dial, a gain. Args: varname (str): Variable name of the comment object. num (float): Value to be set for the object.
AI agents use set_number 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 modifies state within a MaxMSP patch by changing control values. It is reversible (values can be changed again) and creates side effects by altering patch parameters, but does not execute arbitrary code, delete data, or move money. It fits the Write category: creates or modifies data reversibly.
From the tool's definition The tool description explicitly states it "Set[s] the value of a object in MaxMSP" for controls like number boxes, sliders, dials, and gain objects. The function signature accepts a variable name and a numeric value to be assigned.
Documented attack patterns abuse exactly the kind of access set_number 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 set_number:
{
"version": "1",
"default": "deny",
"tools": {
"set_number": {
"limits": [
{
"counter": "set_number_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_number 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.
Set the value of a object in MaxMSP. The object can be a number box, a slider, a dial, a gain. Args: varname (str): Variable name of the comment object. num (float): Value to be set for the 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 set_number: 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.
set_number 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 set_number 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 set_number. 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.
set_number 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.