Skip to content

microsoft/power-platform-skills / plugins/power-pages/skills/manage-firewall

manage-firewall

Unverified

Inspects and configures the web application firewall (WAF) in front of a Power Pages production site. Lists the current state, recommends enabling protection when it is off, and walks the user through adding, updating, or removing custom rules — IP blocks, country blocks, path blocks, and rate limits. Use when the user wants to turn on WAF, block traffic by IP or country, rate-limit login or signup pages, protect pages from brute-force attempts, restrict access to specific paths, review the current firewall configuration, or asks "is my site protected against bots / common web attacks?" — even if they say "add rate limit" or "protect login page" without mentioning "firewall" or "WAF".

FileKindSize
SKILL.mdskill md17.5 KB
references/commands.mdmarkdown11.4 KB
references/rule-reference.mdmarkdown8.5 KB
scripts/delete-rules.jsscript1.8 KB
scripts/disable.jsscript2.8 KB
scripts/enable.jsscript3.0 KB
scripts/get-rules.jsscript1.7 KB
scripts/get-status.jsscript1.6 KB
scripts/set-rules.jsscript2.8 KB
scripts/transform-firewall.jsscript6.4 KB

scripts/set-rules.js

View on GitHub
#!/usr/bin/env node

const {
  resolveContext,
  request,
  parseCliArgs,
  fail,
  hasErrorCode,
  runCli,
} = require('../../../scripts/lib/power-platform-api');

// Service rejects rule names with hyphens, underscores, dots, or spaces (B021).
// Enforce locally so callers get a clear local error before the round-trip.
const RULE_NAME_RE = /^[a-zA-Z][a-zA-Z0-9]*$/;
const REQUEST_TIMEOUT_MS = 240_000; // 4 min — rule creation exceeds the 15s default.

const HELP = `set-rules.js — Creates or updates specific firewall rules.
Only include the rules being added or modified; existing rules not in the payload are preserved.

Usage:
  node set-rules.js --portalId <portal-id> --data-inline '<json>'

Flags:
  --portalId      Power Platform API portal identifier (resolved during prerequisites)
  --data-inline   JSON string with the CustomRules and/or ManagedRules to create or update
  --help          Show this help message

Exit codes:
  0  Success
  2  Sign-in required
  4  Unsupported (trial site or region restriction)
  1  Other failure

Example:
  node set-rules.js --portalId <portal-id> --data-inline '<json-payload>'
`;

function validateRuleNames(payload) {
  if (!Array.isArray(payload.CustomRules)) return;
  for (const rule of payload.CustomRules) {
    if (rule.name && !RULE_NAME_RE.test(rule.name)) {
      fail(
        `Invalid rule name "${rule.name}": must start with a letter and ` +
          'contain only letters and numbers.',
        1
      );
    }
  }
}

async function main() {
  if (process.argv.includes('--help')) {
    process.stdout.write(HELP);
    return;
  }

  const args = parseCliArgs(process.argv);
  const portalId = args.portalId;
  const dataInline = args['data-inline'] || args.dataInline;

  if (!portalId || !dataInline) {
    fail(
      "Usage: node set-rules.js --portalId <portal-id> --data-inline '<json-payload>'",
      1
    );
  }

  let payload;
  try {
    payload = JSON.parse(dataInline);
  } catch (err) {
    fail(`Failed to parse JSON: ${err.message}`, 1);
  }
  if (!payload || typeof payload !== 'object' || Array.isArray(payload)) {
    fail('--data-inline must be a JSON object containing CustomRules and/or ManagedRules.', 1);
  }
  validateRuleNames(payload);

  const ctx = resolveContext();
  if (ctx.error) fail(ctx.error, 2);

  const res = await request({
    context: ctx,
    method: 'PUT',
    path: `/websites/${portalId}/createWafRules`,
    body: payload,
    timeout: REQUEST_TIMEOUT_MS,
  });

  if (hasErrorCode(res, 'B022', 'B023')) {
    fail(`Firewall not available: ${res.error?.message || ''}`, 4);
  }
  if (!res.ok) {
    fail(`Set firewall rules failed (${res.statusCode}): ${res.error?.message || ''}`, 1);
  }

  process.stdout.write(JSON.stringify({ status: 'ok', body: res.body }) + '\n');
}

runCli(module, main);
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall