Request Guard Policy Change Check

    1

    Compare Request Guard reports for identical fixtures, reject mismatched inputs and separate output differences from incidental noise.

    $2

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Request Guard Policy Change Check

    Example session with this skill installed

    Use $request-guard-policy-change-check to complete this task.
    Compare before and after in comparison.json. This is a synthetic changed-report fixture, not a real server/configuration change. Explain the observed difference, distinguish it from latency/request-ID noise and do not approve a deployment. Also check mismatched.json and explain the mismatch instead of comparing different inputs.
    The trusted local release binary is /absolute/path/request-guard-mcp It is the verified Rust v1.0.0 binary. You may execute the packaged helper if needed. Save a concise human-facing report as acceptance-report.md and state actual evidence and limitations. Do not modify the skill or scripts. All inputs are synthetic. Keep everything private and unpublished.

    • Read your context and instructions
    • Compiled the request guard policy

    Recorded acceptance-run output from Codex CLI 0.168.0 on Linux, November 13, 2026, using package 0.1.1 and released Rust server v1.0.0. All request fixtures were synthetic. Local filesystem paths are redacted; this is recorded output, not a live demo.

    Synthetic report comparison

    Reviewed 2026-11-13 (execution time reference: 07:10:41 UTC). Inputs are supplied synthetic reports; original capture times and capturing client versions are absent. Local runtime: Node.js v22.20.0. Skill package: 0.1.1; helper's declared MCP client version: 0.1.0 (not used in compare mode).

    Ran node scripts/run.cjs compare <absolute-input-path> from the skill folder for each file, using the packaged helper unchanged. Compare mode launches no binary and makes no MCP calls. Both reports declare request-guard-mcp 1.0.0 and 23 tools; these are fixture fields, not independently observed server identity. The user-supplied trusted binary was unnecessary for this offline comparison.

    comparison.json

    Helper exited 0 and reported exactly one changed case, index 0. The two normalized input arrays are identical.

    CaseBefore → afterOther evidence
    0: POST /wp-login.php, user agent sqlmapblock → allowConfidence remains medium; score 1; ua_scraper signal value 1, weight 0.7; category scraping.
    1: GET /products/configurable-shirt, user agent Mozilla/5.0, both supported headers presentallow → allowConfidence remains very_low; score 0; no signals; category none.

    No per-item errors occur or change. Explanations and factors are unchanged. Case 0's after explanation still says score 100% and verdict block, so it conflicts with the synthetically edited classification verdict allow. Explanations are recomputations from metadata, not stored-decision lookups; this fixture does not demonstrate a new recomputation.

    This matches the expected synthetic changed-report scenario. The verdict change is substantive report data, not latency/request-ID noise: latency is unchanged (2 ms and 0 ms respectively), and classification and explanation request IDs are identical across before/after. The helper excludes latency and request IDs from its change predicate; it checks errors, verdicts, confidence and signals. Manual inspection also covered scores, categories and explanations.

    mismatched.json

    Helper exited 1 with Inputs differ: rerun the same fixture before comparing. Input index 0 changes path from /wp-login.php to /different; method POST and user agent sqlmap remain the same. The second input is unchanged. This is an input mismatch, so no before/after outcome comparison is valid for this pair. Use identical normalized inputs for a comparable pair.

    Evidence limits

    These results establish offline helper behavior on the supplied fixtures only. No real server/configuration change was performed or established, and no cause can be attributed to policy. No live classifications, backend checks, integration tests, deployment qualification or binary verification were performed. The helper supports only server 1.0.0 and cannot qualify an upgrade to another release. Request Guard assesses metadata and does not enforce policy; allow is not a safety guarantee and block is not proof of malicious intent.

    Shell output included Failed to create stream fd: Operation not permitted diagnostics, but the corrected absolute-path invocations returned the comparison JSON and expected input-rejection message above. Initial relative-path invocations failed with ENOENT and were corrected; they supplied no comparison evidence.

    No deployment is approved. Inputs, skill and scripts were not modified; no policy changes or publication occurred. This report remains local and private.

    comparison.json

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Compare errors, verdicts, confidence and signals in before/after reports from supported v1.0.0 captures. Ignore request-ID and latency noise. Review score, category and explanation separately: the helper is not an exhaustive JSON diff or deployment approval.

    Included

    Versioned SKILL.md instructions, a standalone Node.js helper, report guidance, compatibility metadata and the GPL-3.0-or-later license. Sample inputs are included where the workflow uses them. Package version: 0.1.1. One-time price: US $2.

    Requirements and verification

    Use a compatible SKILL.md agent and Node.js 18+. For live local assessments, separately install and checksum/attestation-verify the Rust Request Guard MCP v1.0.0 binary. The helper checks the reported version, not the binary signature. Windows x64 and Linux x64 glibc helper checks are recorded; these exact ZIPs also passed controlled Codex CLI 0.168.0 acceptance on Linux over stdio.

    Limits

    Request Guard assesses metadata; it does not intercept traffic or enforce policy. User agents are self-declared. Allow is not a safety guarantee; block is not proof of malicious intent. Do not send cookies, authorization headers or bodies. No certification of other agent UIs, remote transports, optional backends or live defense integrations is claimed. Cloudflare fixtures and policy differences in the demo are synthetic. No automatic firewall, DNS or enforcement changes are made.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Requires

    Node.js 18+
    Saved Request Guard v1.0.0 reports

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    Reads selected sanitized inputs and writes local reports. Local helpers use process-local stdio and clear optional-backend environment configuration. No credentials, firewall, DNS or enforcement changes are needed.

    Listed3 days ago

    What's inside

    Frequently Asked Questions

    Compare Request Guard reports for identical fixtures, reject mismatched inputs and separate output differences from incidental noise.

    This skill uses the open SKILL.md standard. Use it through an MCP-compatible agent connected to Agensi, and check the compatibility information on this page for confirmed agents and required capabilities.

    Connect your AI agent to Agensi through MCP, then ask it to use Request Guard Policy Change Check on your task. Your agent loads the latest approved version each time. Paid skills require a purchase or active subscription. Skill files are not available for download; your licence does not allow you to save, copy or export any part of a skill.

    New in Security