Add user access to an agent with crypto payment
AI agents use atxp_add_user_to_agent to create or update resources in MoluAbi MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MoluAbi MCP Server environment.
The tool performs two operations: (1) modifying agent access by adding users (Write), and (2) processing a crypto payment (Financial). Per the rules, Financial > Write, so this should be classified as Financial. However, the description emphasizes the access-granting aspect with payment as a secondary mechanism.
From the tool's definition Tool name 'add_user_to_agent' and description 'Add user access to an agent with crypto payment' indicates the tool modifies user access control lists and initiates payment transactions.
Attacks that exploit this kind of access
Add user access to an agent with crypto payment. It is categorised as a Write tool in the MoluAbi MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MoluAbi MCP Server MCP server in PolicyLayer and add a rule for atxp_add_user_to_agent: 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_add_user_to_agent is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the atxp_add_user_to_agent 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_add_user_to_agent. 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_add_user_to_agent 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 →