Commission a new device using QR code or manual pairing code.
AI agents invoke commission_with_code to trigger actions in Matter. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Commissioning a device involves initiating a pairing/onboarding process that establishes persistent network membership and trust relationships with the Matter fabric. This is an external operation with significant side effects (device joins the network, credentials are exchanged), but it is not purely destructive or financial.
From the tool's definition Commission a new device using QR code or manual pairing code
Documented attack patterns abuse exactly the kind of access commission_with_code gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Matter, and nothing reaches the server without passing your rules. This is the rule we recommend for commission_with_code:
{
"version": "1",
"default": "deny",
"tools": {
"commission_with_code": {
"limits": [
{
"counter": "commission_with_code_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} commission_with_code stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Commission a new device using QR code or manual pairing code. It is categorised as a Execute tool in the Matter MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Matter MCP server in PolicyLayer and add a rule for commission_with_code: 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 Matter. Nothing to install.
commission_with_code is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the commission_with_code 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 commission_with_code. 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.
commission_with_code is provided by the Matter MCP server (mattercoder/matter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Matter, 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.
15 Matter tools catalogued and risk-classified — across an index of 43,000+ MCP servers.