Skip to main content

Agents and MCP

Reference material for autonomous LLM agents and the Model Context Protocol (MCP) that connects them to tools, data, and other agents. Four files, each in the two-track format (Offensive / Defensive).

Why This Exists​

An agent is an LLM that can take actions: call tools, read and write files, send messages, run code, and delegate to other agents. MCP is the emerging standard for exposing those capabilities to a model in a uniform way. Both change the threat model fundamentally: an injection is no longer a bad answer, it is a tool call with the agent's credentials. This subcategory documents the agent and MCP attack surface, the exploitation recipes, and the controls that keep an agent inside its intended authority.

Format​

Every file uses the two-track structure:

## 1. Overview
## 2. Reconnaissance / Enumeration
## 3. Common Attack Vectors
## 4. Exploitation Recipes
## 5. Post-Exploitation
## 6. Preventive Controls (Defensive)
## 7. Detection Controls (Defensive)
## 8. Verification
## 9. AI-Specific Considerations
## 10. Production Notes
## 11. References

Files​

#TopicFile
01Agent Fundamentals01 Agent-Fundamentals.md
02MCP Protocol and Attacks02 MCP-Protocol.md
03Agent Injection03 Agent-Injection.md
04Agent Defense04 Agent-Defense.md

Scope​

  • 01 Agent-Fundamentals: agent loop, planning, memory, tool calling, multi-agent topologies, MCP basics.
  • 02 MCP-Protocol: MCP servers, transports (stdio, SSE, streamable HTTP), tool/resource/prompt primitives, confused deputy, server spoofing, supply chain.
  • 03 Agent-Injection: tool-call injection, goal hijacking, memory poisoning, multi-agent propagation, confused-deputy chains.
  • 04 Agent-Defense: tool allow-lists, per-tool authorization, human in the loop for high-impact actions, sandboxing, audit and replay.

References​

Authorized Use Only​

For authorized security testing and educational purposes only. See SECURITY.md in the repository root.