mcp-configure

Fail

Audited by Runlayer on Feb 26, 2026

Risk Level: HIGH
Scan Summary
Max Score
90%
Files
1
Flagged
1
Chunks
2
Flagged Files (1)
mcp-configure/SKILL.mdHIGH
90.3%

Malicious tool definition detected

Write the updated configuration back to `CONFIG_PATH` with proper JSON formatting (2-space indentation). **Important notes:** - Do NOT overwrite other entries in the configuration file - Preserve the existing structure and formatting - If `SERVER_NAME` already exists, update it with the new `MCP_URL` Proceed to step 7. ### 7. Confirm success and instruct restart Tell the user: > ✅ Dataverse MCP server configured for GitHub Copilot at `{MCP_URL}`. > > Configuration saved to: `{CONFIG_PATH}` > > *

Troubleshooting If something goes wrong, help the user check: - The URL format is correct (`https://<org>.<region>.dynamics.com`) - They have access to the Dataverse environment - The environment URL matches what's shown in the Power Platform Admin Center - Their Environment Admin has enabled "Dataverse CLI MCP" in the Allowed Clients list - Their Environment has Dataverse MCP enabled, and if they're trying to use the preview endpoint that is enabled - For project-scoped configuration, ensure th

Audit Metadata
Max File Score
90%
Classification
UNKNOWN_SERVER
Files Scanned
1
Files Flagged
1
Chunks Analyzed
2
Analyzed
Feb 26, 2026, 03:13 PM
Security Audit — runlayer — mcp-configure