AI agents call list-all-registered-moxis-instances to retrieve information from Moxis without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation as it retrieves and queries data about registered instances without modifying, deleting, or executing anything. The severity is medium rather than low because the returned instance list could reveal infrastructure details or sensitive deployment information that an attacker could use for reconnaissance or targeting, but the tool itself performs no destructive or financial operations.
From the tool's definition The tool "list-all-registered-moxis-instances" returns/retrieves a list of already registered MOXIS instances. The description states it will "Return the MOXIS instances, which are already registered" — a retrieval operation with no side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Return the MOXIS instances, which are already registered. It is categorised as a Read tool in the Moxis MCP Server, which means it retrieves data without modifying state.
Register the Moxis MCP server in PolicyLayer and add a rule for list-all-registered-moxis-instances: 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.
list-all-registered-moxis-instances is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list-all-registered-moxis-instances 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 list-all-registered-moxis-instances. 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.
list-all-registered-moxis-instances 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 →