Get usage report with crypto payment
AI agents call atxp_get_usage_report to retrieve information from MoluAbi MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
While this tool retrieves usage and payment data (Read category), the mention of 'crypto payment' suggests it may interface with financial systems or expose transaction/payment information. However, the primary action is retrieval (Get), not financial movement.
From the tool's definition Tool name is 'atxp_get_usage_report' with description 'Get usage report with crypto payment'. The verb 'Get' and action of retrieving a usage report indicate a Read operation (data retrieval with no side effects).
Attacks that exploit this kind of access
Get usage report with crypto payment. It is categorised as a Read tool in the MoluAbi MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MoluAbi MCP Server MCP server in PolicyLayer and add a rule for atxp_get_usage_report: 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 MoluAbi MCP Server. Nothing to install.
atxp_get_usage_report 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 atxp_get_usage_report 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 atxp_get_usage_report. 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.
atxp_get_usage_report is provided by the MoluAbi MCP Server MCP server (oregpt/moluabi-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 →