Register a new agent on the marketplace. Requires $0.10 USDC payment. Set NULLPATH_WALLET_KEY env var.
AI agents use register_agent to commit financial operations through nullpath MCP Client — usually the final step of a payment, billing, or trading workflow. A call moves real money.
The tool explicitly commits a financial transaction — a $0.10 USDC payment — using a wallet private key. This constitutes a real monetary obligation, placing it in the Financial category. Misuse could drain funds or register unauthorized agents, warranting high severity.
From the tool's definition 'Register a new agent on the marketplace. Requires $0.10 USDC payment. Set NULLPATH_WALLET_KEY env var.'
Attacks that exploit this kind of access
Register a new agent on the marketplace. Requires $0.10 USDC payment. Set NULLPATH_WALLET_KEY env var. It is categorised as a Financial tool in the nullpath MCP Client MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the nullpath MCP Client MCP server in PolicyLayer and add a rule for register_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 nullpath MCP Client. Nothing to install.
register_agent is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the register_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 register_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.
register_agent is provided by the nullpath MCP Client MCP server (nullpath-labs/mcp-client). 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 →