AI agents use set_client_note to create or update resources in UniFi MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UniFi MCP environment.
This tool modifies client data (notes) but the change is fully reversible—notes can be edited or deleted without side effects. It does not execute code, delete data irreversibly, move funds, or trigger external systems. It fits the Write category (creates or modifies data reversibly).
From the tool's definition Tool name 'set_client_note' indicates modifying metadata (a note/annotation) associated with a client device. The UniFi context suggests this adds or updates a text field on a client record.
Documented attack patterns abuse exactly the kind of access set_client_note gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and UniFi MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for set_client_note:
{
"version": "1",
"default": "deny",
"tools": {
"set_client_note": {
"limits": [
{
"counter": "set_client_note_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_client_note 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_client_note. It is categorised as a Write tool in the UniFi MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the UniFi MCP server in PolicyLayer and add a rule for set_client_note: 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 UniFi MCP. Nothing to install.
set_client_note 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_client_note 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_client_note. 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_client_note is provided by the UniFi MCP server (jmagar/unifi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from UniFi MCP, 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.
29 UniFi MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.