Is @microsoft/agents-a365-tooling safe?
- Node.js filesystem read
- Node.js network egress
What to do: Nothing here argues against installing it. Grant the capabilities it lists only if you expect the tool to need them.
@microsoft/agents-a365-tooling is an npm package analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators. It can: filesystem read and network egress — capabilities are what the code can do, not a verdict on intent. Risk score 0/100 (low).
@microsoft/agents-a365-tooling 2.0.0-preview.1
Automated static-analysis result. It can contain false positives and false negatives, and is not a claim about the intent of @microsoft/agents-a365-tooling's authors. Report a false positive.
Behavioral traits
How this component maps to the CSA agentic threat model. Descriptive — it never affects the risk score.
Findings (2)
The component reads files from disk.
const jsonContent = fs.readFileSync(manifestPath, 'utf-8');
Why it matters: Usually legitimate, but worth confirming it can't be steered into reading sensitive files.
Fix: Confirm which files are read and that paths cannot be influenced by untrusted input to reach sensitive locations.
The component makes outbound network requests.
const axios_1 = __importDefault(require("axios"));import axios from 'axios';
await axios.post(endpoint, request, {if (axios.isAxiosError(err)) {const response = await axios.get(configEndpoint, {Why it matters: Usually legitimate, but confirm the destinations are expected and no sensitive data leaves.
Fix: Confirm the destination hosts are expected and that no sensitive data is sent off-host.
Check your own component
Run the same evidence-backed scan on any MCP server, agent skill, or package.
Scan your own componentHow we determine this: deterministic static analysis (regex + AST), evidence-anchored, no code execution. Methodology →