A2A SDK for Rust 0.3
Last reviewed Sep 19, 2026
Prompt Details
Prompt Composition
2prompts
- Rust 1.98136 lines · 3.6K tokens
- A2A SDK for Rust 0.363 lines · 2.9K tokens
Total199 lines · 6.5K tokens
CWE Coverage
- 20
- 22
- 59
- 78
- 89
- 90
- 117
- 125
- 190
- 197
- 201
- 208
- 209
- 250
- 288
- 295
- 306
- 319
- 338
- 347
- 362
- 367
- 378
- 407
- 409
- 416
- 502
- 532
- 639
- 643
- 674
- 770
- 772
- 787
- 807
- 829
- 862
- 863
- 918
- 942
- 1336
- 1395
- 1427
Prompt Preview
Apply the Rust 1.98 baseline first. These rules cover a2a-lf 0.3, which implements A2A protocol 1.0, and its companion crates. They were checked against 0.3.0 with a2a-client-lf 0.2.3, a2a-server-lf 0.4.3, a2a-pb 0.2.0, a2a-grpc 0.3.5, and a2a-slimrpc 0.2.7. The workspace declares Rust 1.85 and edition 2024; verify the resolved dependency graph against the supported toolchain required by the baseline.
Discovery and client credentials
- Allowlist discovery origins before
AgentCardResolver::resolveand passAgentCardResolver::new(Some(client))an HTTP client with explicit redirect, proxy, and timeout policy. Use a capped HTTPS fetch-and-decode path when accepting untrusted cards:resolvedeserializes the response without a card-size limit. - Validate every
supported_interfacesendpoint, binding, and protocol version beforeA2AClientFactory::create_from_card. Useno_defaults()and register only approved factories;preferred_bindingsranks candidates without excluding other bindings or fallback. Reject malformed versions before negotiation. - Supply policy-configured clients to
JsonRpcTransportFactory::newandRestTransportFactory::newas well as discovery. A custom discovery client does not configure the factory's default HTTP transports. For untrusted peers, add bounded response decoding through a customTransport, including JSON-RPC version, request-ID, and result/error validation. - Verify
AgentCard.signatureswith provider-trusted keys, allowed JWS algorithms, and the protocol's JCS canonicalization before relying on signed identity.