describe_auditor
Fetch an auditor's agent card (GET /agent on its origin): who it claims to be, what it charges, and on which network. Free, unauthenticated, and never trusted — the seal it returns later is what gets verified.
This record as markdown: /tools/0x402-mcp/describe-auditor.md
What describe_auditor does on 0x402
AI agents call describe_auditor 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 |
|---|---|---|---|
url | string | — | Auditor endpoint; the card is read from /agent on its origin. Defaults to ACU_AUDITOR_URL. |
Parameters from the server's own tool schema.
Why describe_auditor is rated Low
Even though describe_auditor 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 signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs describe_auditor 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 describe_auditor, this is the rule to start with:
describe_auditor 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 describe_auditor call is checked against it from then on.
Questions about describe_auditor
Fetch an auditor's agent card (GET /agent on its origin): who it claims to be, what it charges, and on which network. Free, unauthenticated, and never trusted — the seal it returns later is what gets verified. It is categorised as a Read tool in the 0x402 MCP Server, which means it retrieves data without modifying state.
describe_auditor accepts 1 parameter: url. 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 describe_auditor: 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.
describe_auditor 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 describe_auditor 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 describe_auditor. 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.
describe_auditor 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