AI agents use set-alias-instance to create or update resources in Moxis — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Moxis environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | url of the MOXIS instance to login to |
alias | string | Yes | alias to assign to the instance |
Parameters from the server's own tool schema.
The tool sets/creates an alias, which is a reversible data modification operation. It does not execute code, delete data, or move money. The blast radius is low—modifying an instance alias affects only that instance's naming/identification and can be easily changed or undone. Confidence is high given the clear intent, though the description lacks detail about parameters and scope.
From the tool's definition Tool name 'set-alias-instance' and description 'set alias for MOXIS instance' indicate modification of metadata (an alias) associated with a MOXIS instance. This is a write operation that creates or modifies data reversibly.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
set alias for MOXIS instance. It is categorised as a Write tool in the Moxis MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
set-alias-instance accepts 2 parameters: url, alias. Required: url, alias. The full parameter table on this page comes from the server's own tool schema.
Register the Moxis MCP server in PolicyLayer and add a rule for set-alias-instance: 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 Moxis. Nothing to install.
set-alias-instance 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-alias-instance 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-alias-instance. 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-alias-instance is provided by the Moxis MCP server (@xitrust-pub/moxis-mcp-server). 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 →