Update metadata for a single annotation (status/intent/severity/comment).
AI agents use onui_update_annotation_metadata to create or update resources in onUI — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your onUI environment.
This is a Write operation because it creates or modifies data reversibly—updating annotation metadata is a non-destructive change that can be undone or corrected. The severity is medium because misuse could corrupt or spam annotation metadata across UI elements, affecting team workflows, but does not irreversibly delete data or access sensitive financial/authentication systems.
From the tool's definition Tool name includes 'update' and description states it modifies metadata fields (status/intent/severity/comment) for annotations.
Documented attack patterns abuse exactly the kind of access onui_update_annotation_metadata gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and onUI, and nothing reaches the server without passing your rules. This is the rule we recommend for onui_update_annotation_metadata:
{
"version": "1",
"default": "deny",
"tools": {
"onui_update_annotation_metadata": {
"limits": [
{
"counter": "onui_update_annotation_metadata_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}onui_update_annotation_metadata 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.
Update metadata for a single annotation (status/intent/severity/comment). It is categorised as a Write tool in the onUI MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the onUI MCP server in PolicyLayer and add a rule for onui_update_annotation_metadata: 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 onUI. Nothing to install.
onui_update_annotation_metadata 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 onui_update_annotation_metadata 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 onui_update_annotation_metadata. 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.
onui_update_annotation_metadata is provided by the onUI MCP server (onllm-dev/onui). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 onUI tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 onUI tools catalogued and risk-classified — across an index of 42,500+ MCP servers.