autogen-multiagent-security

Name: autogen-multiagent-security
Availability: InStock
Author: Akshay

Detects and mitigates inter-agent attack vectors in AutoGen multi-agent systems.

4|Updated Apr 27, 2026

Search Tags:#security #multi-agent #orchestration #sandboxing #audit-logging #prompt-injection #autogen

Ready to run

npx skills add https://github.com/maruakshay/mii-ai-security --skill autogen-multiagent-security

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: autogen-multiagent-security
Source: https://github.com/maruakshay/mii-ai-security/tree/main/skills/autogen-multiagent-security
Command: npx skills add https://github.com/maruakshay/mii-ai-security --skill autogen-multiagent-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review an AutoGen multi-agent system and apply risk checks to detect and mitigate inter-agent spoofing, boundary bypass, and code-execution threats.

Core Features & Use Cases

Inter-agent trust auditing across planner, orchestrator, executor, and critic roles.
Detection of spoofed directives, boundary violations, and sandbox escape attempts.
Guidance for implementing validation, isolation, and logging controls in multi-agent workflows.

Quick Start

Review an AutoGen multi-agent setup and apply risk checks to detect inter-agent spoofing, boundary bypass, and code-execution threats.

Frequently Asked Questions about autogen-multiagent-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I secure multi-agent AutoGen systems against inter-agent attacks?▼

Securing multi-agent AutoGen systems involves applying risk checks across orchestrator, planner, executor, and critic agents to detect message spoofing, trust boundary violations, and code execution escalations.

What are common prompt injection and spoofing risks in multi-agent orchestration?▼

Common risks in multi-agent orchestration include spoofed directives between agents, trust boundary bypasses, and unauthorized sandbox escape attempts that escalate code execution privileges across planner and executor roles.

How do I audit trust boundaries in an AutoGen multi-agent workflow?▼

Auditing trust boundaries in AutoGen involves reviewing message flows between orchestrator, planner, executor, and critic agents to identify spoofed directives and validate task schemas against unauthorized actions.

Does AutoGen support sandboxing and audit logging for executor agents?▼

AutoGen requires external enforcement for strict isolation and auditable logging to sandbox executor agents effectively, preventing unauthorized code execution escalations and ensuring remediation guidance.

What is the best way to prevent code execution escalation in multi-agent LLM frameworks?▼

Preventing code execution escalation in multi-agent LLM frameworks requires enforcing a validated task schema, applying strict isolation boundaries, and implementing auditable logging across all agent roles.

When should I apply task schema validation in multi-agent security?▼

You should apply task schema validation in multi-agent security whenever autonomous agents interact, ensuring that orchestrator and executor agents process only authorized directives and preventing boundary violations.