Set WiFi credentials for device commissioning.
AI agents use set_wifi_credentials to create or update resources in Matter — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Matter environment.
This tool creates or modifies WiFi credentials on a Matter device, which is a reversible Write operation. It is not Destructive (credentials can be changed), not Execute (does not run arbitrary code), not Financial, and not merely Read.
From the tool's definition Tool name 'set_wifi_credentials' and description 'Set WiFi credentials for device commissioning' indicate modification of device configuration state. The verb 'Set' combined with 'credentials' shows this creates or modifies sensitive authentication data.
Documented attack patterns abuse exactly the kind of access set_wifi_credentials 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 set_wifi_credentials:
{
"version": "1",
"default": "deny",
"tools": {
"set_wifi_credentials": {
"limits": [
{
"counter": "set_wifi_credentials_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_wifi_credentials 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 WiFi credentials for device commissioning. It is categorised as a Write tool in the Matter MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Matter MCP server in PolicyLayer and add a rule for set_wifi_credentials: 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.
set_wifi_credentials 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_wifi_credentials 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_wifi_credentials. 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_wifi_credentials 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.