docs(blog): compress images to fix GitHub Pages deployment (#6339)
|
After Width: | Height: | Size: 378 KiB |
|
Before Width: | Height: | Size: 2.6 MiB |
|
After Width: | Height: | Size: 280 KiB |
|
Before Width: | Height: | Size: 4.9 MiB |
|
Before Width: | Height: | Size: 100 KiB After Width: | Height: | Size: 73 KiB |
|
After Width: | Height: | Size: 223 KiB |
|
Before Width: | Height: | Size: 2.1 MiB |
|
After Width: | Height: | Size: 229 KiB |
|
Before Width: | Height: | Size: 871 KiB |
@@ -6,7 +6,7 @@ authors:
|
||||
- alex
|
||||
---
|
||||
|
||||

|
||||

|
||||
|
||||
|
||||
In [our previous blog post](https://block.github.io/goose/blog/2025/03/31/securing-mcp/) we detailed the Model Context Protocol (MCP) system and discussed some security concerns and mitigations. As a brief recap, MCP provides agents with a means to accomplish tasks using defined tools; reducing the burden of using complex and varied APIs and integrations on the agent.
|
||||
@@ -32,7 +32,7 @@ That’s a lot of words, here’s a picture instead, *(Typos Provided for free\*
|
||||
|
||||
<div style={{textAlign: "center"}}>
|
||||
|
||||

|
||||

|
||||
|
||||
|
||||
<em>Example of a successful CSRF attack chain with by a very devious hacker</em>
|
||||
@@ -43,7 +43,7 @@ Today, CSRF is largely mitigated by **browser-enforced CORS (Cross-Origin Resour
|
||||
|
||||
<div style={{textAlign: "center"}}>
|
||||
|
||||

|
||||

|
||||
|
||||
|
||||
<em>CORS mitigated the CSRF attack leaving a very sad (but still devious) hacker. Note: in practice the CORS check would likely happen during preflight.</em>
|
||||
@@ -212,7 +212,7 @@ To handle these threats we propose **removing** **all tool-call responses from t
|
||||
|
||||
<div style={{textAlign: "center"}}>
|
||||
|
||||

|
||||

|
||||
|
||||
|
||||
<em>Our workflow imagined (mostly) correctly with ♥️ by ChatGPT</em>
|
||||
|
||||