AI agents call moxis-help 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.
A help/introduction tool only displays static informational content about the plugin. It has no side effects, does not modify data, and poses minimal risk if misused.
From the tool's definition 'Simple introduction to moxis mcp plugin' — this is a help/documentation tool that retrieves informational content
Attacks that exploit this kind of access
Simple introduction to moxis mcp plugin. 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 moxis-help: 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.
moxis-help 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 moxis-help 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 moxis-help. 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.
moxis-help 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 →