microsoft-foundry@r7
VERIFIED· install onlyPublisher claims: "Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent, managed harness agent, Copilot harness, voice agent, create/update/invoke/evaluate agent, add tool to agent, agent insights, batch/continuous eval, continuous monitoring, agent CI/CD, optimize/improve prompt, optimize agent instructions, Agent Optimizer, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure-prepare)." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Bundled scripts ran with no arguments; no agent task scenario for this bundle.- Tested
- 8 of 15 bundled scripts run with no arguments (the rest were not run: per-bundle cap), with decoy credentials in the environment · every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What changed since r1
vet-skills diff microsoft-foundry r1 r7This version reaches for something r1 did not: 1 new host (azure.com) · 2 new credential variables (API_KEY, AZURE_OPENAI_API_KEY). Compared from the two recorded runs, not from source.
- New hosts
- azure.com
- New credential variables
- API_KEY, AZURE_OPENAI_API_KEY
r1 was not run in the sandbox (static only); the comparison covers what static analysis recorded only.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is microsoft-foundry@r7 safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-17 and scored it 90/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 1 s · 2 scenarios · 0 deviationsStatic findings
result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.parser.add_argument("--output", default="eval_results.json", help="Output file")Fix: Put hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.exec(compile(source, grader_path, "exec"), namespace)Fix: Put hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.| `Microsoft.DefaultV2` | Updated default with jailbreak + protected material | No |Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.{ "name": "Jailbreak", "enabled": true, "blocking": true, "source": "Prompt" }Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.