Skip to content
KitploitKITPLOIT
工具漏洞利用博客
Log in
提交
工具漏洞利用博客
提交

黑客、渗透测试和网络安全工具,武装您的安全武器库!

Kitploit 是一个黑客、网络安全和渗透测试工具的目录。发现最新的项目更新,查找漏洞、分析系统、自动化测试并加强你的安全。

订阅源联系隐私© 2026 Kitploit

工具目录

分类

查看所有分类
Loading categories
acp-framework-en — 代理控制协议(ACP)——官方英文规范。面向自主AI代理的密码学可验证授权架构。 | Kitploit
工具/GitHubGitHub/chelof100/acp-framework-en
身份验证与授权密码学云安全身份与访问管理 (IAM)供应链安全论文与研究学习与教育AI 安全
GitHubchelof100/acp-framework-en

acp-framework-en

代理控制协议(ACP)——官方英文规范。面向自主AI代理的密码学可验证授权架构。

查看仓库
2943个月前尚未审核
分享
内容在请求的语言中不可用。显示英文版本。

ACP — Agent Control Protocol

Admission control for agent actions.

Before any agent mutates system state, ACP answers four questions: Who is this agent? What are they authorized to do? Is this action policy-compliant? Can the outcome be traced to an accountable institution?

Cryptographic identity · Scoped capability tokens · Verifiable delegation chains · Execution proof

Official Website

https://agentcontrolprotocol.xyz

Paper

Agent Control Protocol: Admission Control for Agent Actions Marcelo Fernandez (TraslaIA), 2026

DOI: 10.5281/zenodo.19672575  ·  arXiv: 2603.18829


Research Series

ACP is the published foundation of a ten-paper series on formal agent governance. Each paper addresses a distinct layer of the governance stack.

PaperTitleRepoStatus
Paper 0Atomic Decision Boundariesdecision-boundary-modelZenodo · arXiv:2604.17511
Paper 1Agent Control Protocol (ACP) — this repoacp-framework-enZenodo · arXiv:2603.18829
Paper 2From Admission to Invariants (IML)iml-benchmarkZenodo · arXiv:2604.17517
Paper 3/4Irreducible Governance Structuregovernance-structureZenodo · arXiv: on appeal
Paper 5Reconstructive Authority Model (RAM)reconstructive-authority-modelZenodo · arXiv:2604.22898
Paper 6Operationalizing Reconstructive Authorityoperationalizing-ramZenodo · arXiv:2605.23935
Paper 7Closing the Execution Gap (Empirical)agent-governance-appliedZenodo · arXiv: on appeal
Paper 8Identity-Bound Governance (APB)identity-bound-governanceZenodo · arXiv: on appeal
Paper 9MCP-Native Governancemcp-governed-agentsZenodo · arXiv: pending
Paper 10Non-Blocking Governancenon-blocking-governanceZenodo · arXiv: pending

Series logic: Paper 0 proves when admissibility can be guaranteed → Paper 1 (ACP) builds the protocol → Paper 2 detects drift invisible to enforcement → Paper 3/4 proves correct enforcement ≠ fair allocation and establishes the irreducibility of the four-layer architecture → Paper 5 (RAM) provides operational closure: when to execute under partial observability → Paper 6 operationalizes RAM as a runtime Recovery Loop → Paper 7 provides the first empirical validation of the full stack on real LangGraph agents → Paper 8 establishes identity-bound accountability for halted agents (Phase II: governance of governance) → Paper 9 deploys that governance transparently at the MCP protocol layer → Paper 10 makes it non-blocking via escrow-based asynchronous human oversight.


Why ACP Exists

Autonomous agents are moving from experimentation into production. They already interact with APIs, enterprise systems, financial infrastructure, and other agents.

When one acts across organizations, several questions immediately arise:

  • Who authorized the agent to act?
  • What capabilities does the agent actually have?
  • What policy allowed the action?
  • What exactly was executed?
  • Can that execution be verified later?
  • Can the full interaction history be reconstructed?

Today, most systems cannot answer these questions reliably.

ACP introduces the infrastructure to answer all of them.


ACP vs Related Protocols

Several initiatives address how autonomous agents interact with systems. Most focus on tool access or communication. ACP focuses on authority, execution verification, and institutional accountability.

ProtocolFocusScope boundary
MCP (Model Context Protocol)Tool access for LLMsAuthority verification, policy enforcement, execution auditability
A2A (Agent-to-Agent)Agent communication patternsInstitutional trust, governance, accountability chain
OpenAI Agents SDKTool orchestrationCross-organization authority, provenance, liability
Agent Client Protocol ¹Runtime client/agent integrationGovernance, delegation chains, verifiable execution history
ACP (Agent Control Protocol)Governance & accountability infrastructure—

ACP addresses a different layer: who authorized the action, under what policy, and who is accountable for the outcome.

ACP vs Policy & Auth Systems

Engineers evaluating ACP often ask: "why not use OPA?" These systems are complementary, not competitive.

SystemWhat it doesWhat ACP adds
OPA (Open Policy Agent)Evaluates policies from data and rulesCryptographic agent identity + delegation chain + execution proof
AWS IAM / Azure RBACStatic permission model for cloud resourcesDynamic agent-to-agent delegation with verifiable chain + ledger
OAuth 2.0 + OIDCUser and service authorization via tokensMulti-hop agent delegation with non-escalation + institutional liability
SPIFFE / SPIRECryptographic workload identityACP builds on workload identity to add capability scoping + governance
ACPAdmission control for agent actions—

OPA can be used as the policy evaluation engine inside an ACP-compliant system. ACP does not replace OPA — it adds the agent identity layer, delegation chain, and execution proof that OPA does not provide.


¹ ACP (Agent Control Protocol) is unrelated to other initiatives sharing the same acronym.


ACP as Admission Control

Kubernetes uses an Admission Controller to intercept API requests before they reach the cluster — evaluating policies, enforcing quotas, rejecting non-compliant operations. ACP applies the same pattern to agent actions.

agent intent
    ↓
[1] Identity check       →  pkg/agent + pkg/hp       (ACP-AGENT-1.0, ACP-HP-1.0)
    ↓
[2] Capability check     →  pkg/ct + pkg/dcma         (ACP-CT-1.0, ACP-DCMA-1.0)
    ↓
[3] Policy check         →  pkg/risk + pkg/psn        (ACP-RISK-3.0, ACP-PSN-1.0)
    ↓
[4] ADMIT / DENY / ESCALATE
    ↓  (if ADMIT)
[5] Execution token      →  pkg/exec                  (ACP-EXEC-1.0)
    ↓
[6] Ledger record        →  pkg/ledger                (ACP-LEDGER-1.3)
    ↓
system state mutation

The difference from Kubernetes: ACP operates across institutional boundaries. An agent from Bank A can be admitted by Bank B without Bank B trusting Bank A's internal infrastructure — only the cryptographic proof matters.


How ACP Works

ACP treats agent interactions as governed operations, not simple requests.

Every interaction passes through six structured stages:

下载工具

最受欢迎

查看全部 →

发现我们社区最常用的工具。

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 终极 OSINT 工具包:调查图谱、置信度评分、别名家族、地图、时间线和报告。49 个模块、400+ 个站点,无需 API 密钥。

    546
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock 一键执行应用(CVE-2026-43499)

    477
  • 3

    ARTEX

    baarai/artex

    基于LLM的多智能体自主渗透测试平台,具备规划器/执行器智能体、资产与探索图谱、MITM流量记录以及漏洞复测功能。

    377
  • 4

    redforge

    cybersecurity91/redforge

    浏览器端红队工具包,包含 102 个离线工具,用于侦察、载荷生成、凭据攻击、加密、编码和交战报告。

    324
  • 5

    estorides

    grisuno/estorides

    并行聚合 99+ 个免费 OSINT 来源,将实体解析为知识图谱,并借助 LLM 辅助分析导出 STIX 2.1、MISP 或 GraphML。

    269
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    AI原生网络安全的行动系统——在这里,意图转化为受治理的执行,证据沉淀为运营记忆,每一次操作都让下一次更出色。

    252

探索所有工具

浏览我们的工具集合

查看所有工具 →