hire_audit
Pay the auditor over x402 and verify the seal B it returns against the six checks (signature, live agentId, subject, request, expiry, attestation). Returns the verified seal, or a refusal naming the check that failed. Without a key this stops at the quote.
This record as markdown: /tools/0x402-mcp/hire-audit.md
What hire_audit does on 0x402
AI agents call hire_audit to retrieve information from 0x402 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
token | string | Yes | ERC-20 contract address on 0G testnet. |
ltvBps | integer | — | The LTV you intend to ask for later. Recorded for the caller; the cap is enforced by underwrite. |
source | string | — | Local Solidity source for the token, if you have it. Never fetched. |
Parameters from the server's own tool schema.
Why hire_audit is rated Low
Even though hire_audit only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHandles credentials or secrets (token)
Attacks that exploit this kind of access
The rule that runs hire_audit safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0x402, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hire_audit, this is the rule to start with:
hire_audit is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 0x402, apply this rule, and every hire_audit call is checked against it from then on.
Questions about hire_audit
Pay the auditor over x402 and verify the seal B it returns against the six checks (signature, live agentId, subject, request, expiry, attestation). Returns the verified seal, or a refusal naming the check that failed. Without a key this stops at the quote. It is categorised as a Read tool in the 0x402 MCP Server, which means it retrieves data without modifying state.
hire_audit accepts 3 parameters: token, ltvBps, source. Required: token. The full parameter table on this page comes from the server's own tool schema.
Register the 0x402 MCP server in PolicyLayer and add a rule for hire_audit: 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 0x402. Nothing to install.
hire_audit 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 hire_audit 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 hire_audit. 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.
hire_audit is provided by the 0x402 MCP server (@0x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0x402, and thousands of servers like it.
This server
Across the catalogue