logout-instance · Moxis MCP: Risk & Policy

WHAT IT DOES

What logout-instance does on Moxis

AI agents use logout-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.

PARAMETERS

Parameter	Type	Required	Description
`id`	string	Yes	url or alias of the MOXIS instance to logout from

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why logout-instance needs a policy

Logging out from a specific instance modifies session/authentication state (terminates a session), which is a reversible write-like operation. It does not delete data, execute code, or involve financial transactions. The blast radius is low since a misuse would only terminate a session for one instance, which can be restored by logging back in.

From the tool's definition logout from one registered MOXIS instance

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

logout-instance Rate-limited

logout-instance 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "logout-instance": {
      "limits": [
        {
          "counter": "logout-instance_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Moxis, so you can run agents against it safely.

FAQ

Questions about logout-instance

What does the logout-instance tool do? +

logout from one registered MOXIS instance, where the url is given as parameter. 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.

What parameters does logout-instance accept? +

logout-instance accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on logout-instance? +

Register the Moxis MCP server in PolicyLayer and add a rule for logout-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.

What risk level is logout-instance? +

logout-instance is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit logout-instance? +

Yes. Add a rate_limit block to the logout-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.

How do I block logout-instance completely? +

Set action: deny in the PolicyLayer policy for logout-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.

What MCP server provides logout-instance? +

logout-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.