intel-a2a-pipeline — $0.25 USDC x402. POST https://conc-exe.xyz/api/concierge-intel-a2a-pipeline
AI agents use intel_a2a_pipeline to commit financial operations through Concierge Intel — usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | object | — | JSON POST body |
paymentSignature | string | — | Base64 PAYMENT-SIGNATURE header after x402 settlement |
Parameters from the server's own tool schema.
Every invocation of this tool commits a financial obligation of $0.25 USDC. The x402 payment mechanism means each call triggers a real monetary transaction. Even though the tool delivers intel (a Read-like function), the Financial dimension takes precedence per severity rules. An AI agent calling this tool repeatedly or inadvertently would incur real financial costs, making it high severity.
From the tool's definition $0.25 USDC x402 — the tool explicitly charges USDC per call via x402 payment protocol, and operates on a pay-per-call DeFi intel server
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
intel-a2a-pipeline — $0.25 USDC x402. POST https://conc-exe.xyz/api/concierge-intel-a2a-pipeline. It is categorised as a Financial tool in the Concierge Intel MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
intel_a2a_pipeline accepts 2 parameters: body, paymentSignature. The full parameter table on this page comes from the server's own tool schema.
Register the Concierge Intel MCP server in PolicyLayer and add a rule for intel_a2a_pipeline: 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 Concierge Intel. Nothing to install.
intel_a2a_pipeline 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 intel_a2a_pipeline 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 intel_a2a_pipeline. 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.
intel_a2a_pipeline is provided by the Concierge Intel MCP server (https://conc-exe.xyz/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
intel_a2a_pipeline is one line of Concierge Intel's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →