List all agents with crypto payment
AI agents call list_agents 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.
This tool retrieves and enumerates agent data without creating, modifying, deleting, or executing operations. While it may expose payment-related information, the action itself is purely informational and read-only. No financial transactions are initiated, no code is executed, and no data is altered. The blast radius of misuse is limited to information disclosure.
From the tool's definition Tool name 'list_agents' combined with description 'List all agents with crypto payment' indicates a retrieval operation that queries and returns information about agents and their payment status.
Attacks that exploit this kind of access
List all agents 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 list_agents: 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.
list_agents 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_agents 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_agents. 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_agents 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 →