Validation Report
IAM Drift Monitor v2.2.0 (Submitted by Jane Doe on March 18, 2026)
❌ Rejected
Your submission failed the automated Exsecute verification pipeline. It will not be signed or listed on the marketplace. Please review the errors below, commit fixes to your repository, and submit a new release tag.
Pipeline Stages
1. Ingestion & Cryptographic Hashing
✔ Passes
Pulled `v2.2.0` from `cloudarmor-sec/iam-drift-monitor`. Generated SHA-256 hashes for 1 manifest, 3 skills, and 4 tool containers.
2. Agent Payload Inspection
✖ Failed
Inspecting `exsecutor.yaml`, token budgets, and skill payloads.
[Error: SCHEMA_VIO_042] Skill Context Limit Exceeded.
Details: The total token length of all Markdown files in `skills/` is 8,450 tokens. This exceeds the maximum platform budget of 8,000 contextual tokens allocated for the Skills layer.
Resolution: Consolidate your skill files or summarize domain heuristics.
3. Tool Sandbox & Network Verification
✖ Failed
Executing standard tool containers in the test sandbox analyzing egress constraints.
[Error: SEC_VIO_EGRESS] Undeclared Egress Domain Attempted.
Target Tool: `exsecute/aws-config-fetcher` (Private bundled tool)
Details: During execution, the tool container attempted an HTTPS connection to `telemetry.cloudarmor.com`. This domain was NOT explicitly declared in the `allowed_domains` section of `tool.yaml`.
Resolution: Add `telemetry.cloudarmor.com` to `allowed_domains`, or remove the telemetry call from the tool.
4. End-to-End LLM Simulation
Skipped
5. Signature Generation
Skipped