ClawHub
Back to skill

Security audit

power-automate-mcp

Security checks for vulnerabilities and agentic risk

Overview

This skill is a disclosed setup guide for connecting an agent to FlowStudio MCP for Power Automate, with expected but sensitive access to the user's automation environment.

Install only if you intend to let an agent work with your Power Automate environment through FlowStudio MCP. Treat the JWT/API key as a secret, avoid pasting it into logs or shared transcripts, and prefer an account whose Power Platform permissions match the actions you want the agent to perform.

A.I.G

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
81% confidence
Finding

This markdown file instructs agents to authenticate using an x-api-key header carrying a JWT token, but it does not include any warning about treating the token as sensitive, avoiding logging it, or protecting it from disclosure. Because markdown files should warn about behaviors affecting privacy or system integrity, the omission is a relevant documentation safety gap.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.