Activate a UI preset bundle by ID. Loads all tokens, component templates, and layout templates. Resolves inheritance (extends) chain automatically, deep-merging parent tokens. Must be called before any correction, validation, or generation tools. Args: - preset_id (string): Folder name in /preset...
AI agents use load_preset to create or update resources in UI Preset MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UI Preset MCP Server environment.
load_preset actively changes session state by activating a preset bundle and deep-merging token chains, which is a stateful write/configuration operation rather than a passive read. It modifies the working environment for subsequent tools. No data is deleted, no code is executed, and no financial action is taken, making Write the most appropriate category.
From the tool's definition 'Activate a UI preset bundle by ID. Loads all tokens, component templates, and layout templates. Resolves inheritance (extends) chain automatically, deep-merging parent tokens. Must be called before any correction, validation, or generation tools.'
Attacks that exploit this kind of access
Activate a UI preset bundle by ID. Loads all tokens, component templates, and layout templates. Resolves inheritance (extends) chain automatically, deep-merging parent tokens. Must be called before any correction, validation, or generation tools. Args: - preset_id (string): Folder name in /presets (e.g. It is categorised as a Write tool in the UI Preset MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the UI Preset MCP Server MCP server in PolicyLayer and add a rule for load_preset: 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 UI Preset MCP Server. Nothing to install.
load_preset 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 load_preset 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 load_preset. 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.
load_preset is provided by the UI Preset MCP Server MCP server (ncsound919/og-glass). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →