AI agents use login-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 | — | alias to assign to the instance |
auths | array | Yes | list of auths to assign to the instance |
Parameters from the server's own tool schema.
Logging into an instance creates or modifies session/authentication state on the server, which is a reversible write operation (a logout tool also exists). It is not purely read-only, but it does not execute code, delete data, or involve finances. Severity is medium because a successful login grants access to potentially sensitive resources and sibling tools with broader impact.
From the tool's definition 'login to MOXIS instance' — establishes an authenticated session on a specific instance
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
login to 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.
login-instance accepts 3 parameters: url, alias, auths. Required: url, auths. 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 login-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.
login-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 login-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 login-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.
login-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 →