Sheyda Kiani Mehr commited on
Commit
3123e36
·
1 Parent(s): 43d5db4
Files changed (1) hide show
  1. README-2.md +0 -59
README-2.md DELETED
@@ -1,59 +0,0 @@
1
- # Hello World Example
2
-
3
- Hello World example agent that only returns Message events
4
-
5
- ## Getting started
6
-
7
- 1. Start the server
8
-
9
- ```bash
10
- uv run .
11
- ```
12
-
13
- 2. Run the test client
14
-
15
- ```bash
16
- uv run test_client.py
17
- ```
18
-
19
- ## Build Container Image
20
-
21
- Agent can also be built using a container file.
22
-
23
- 1. Navigate to the directory `samples/python/agents/helloworld` directory:
24
-
25
- ```bash
26
- cd samples/python/agents/helloworld
27
- ```
28
-
29
- 2. Build the container file
30
-
31
- ```bash
32
- podman build . -t helloworld-a2a-server
33
- ```
34
-
35
- > [!Tip]
36
- > Podman is a drop-in replacement for `docker` which can also be used in these commands.
37
-
38
- 3. Run you container
39
-
40
- ```bash
41
- podman run -p 9999:9999 helloworld-a2a-server
42
- ```
43
-
44
- ## Validate
45
-
46
- To validate in a separate terminal, run the A2A client:
47
-
48
- ```bash
49
- cd samples/python/hosts/cli
50
- uv run . --agent http://localhost:9999
51
- ```
52
-
53
-
54
- ## Disclaimer
55
- Important: The sample code provided is for demonstration purposes and illustrates the mechanics of the Agent-to-Agent (A2A) protocol. When building production applications, it is critical to treat any agent operating outside of your direct control as a potentially untrusted entity.
56
-
57
- All data received from an external agent—including but not limited to its AgentCard, messages, artifacts, and task statuses—should be handled as untrusted input. For example, a malicious agent could provide an AgentCard containing crafted data in its fields (e.g., description, name, skills.description). If this data is used without sanitization to construct prompts for a Large Language Model (LLM), it could expose your application to prompt injection attacks. Failure to properly validate and sanitize this data before use can introduce security vulnerabilities into your application.
58
-
59
- Developers are responsible for implementing appropriate security measures, such as input validation and secure handling of credentials to protect their systems and users.