Request Guard Cloudflare Investigation
Assess a sanitized selected Cloudflare event export and compare Request Guard output with separately supplied Cloudflare context.
$2
Works with the AI Agents you already use
Request Guard Cloudflare Investigation
Example session with this skill installed
Use $request-guard-cloudflare-investigation to complete this task.
Investigate the sanitized selected Cloudflare export in input.json. It is a synthetic fixture, not a live API response. Context: Cloudflare action was managed_challenge. Compare that separately with Request Guard output; do not claim you connected to Cloudflare, fetched real logs or changed security settings.
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 cloudflare
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.
Selected Cloudflare export investigation
Captured: 2026-11-13T07:12:33Z. All inputs are synthetic. One selected event was assessed successfully using the packaged helper in cloudflare mode and the user-designated trusted Rust release binary. Server reported request-guard-mcp v1.0.0; helper client: request-guard-paid-workflow v0.1.0 (skill package v0.1.1). Binary verification was supplied by the user, not independently repeated here.
Observed evidence
The export contains only the three supported fields. Mapping produced:
| Export field | Normalized field | Value |
|---|---|---|
| ClientRequestMethod | method | POST |
| ClientRequestPath | path | /wp-login.php |
| ClientRequestUserAgent | user_agent | sqlmap |
Request Guard returned
block, confidence
medium, score
1, threat category
scraping. Its sole reported signal was ua_scraper, value 1, weight 0.7: “User-agent matches scraping tool pattern.” The separate explanation recomputed from the same metadata reported that signal as 100% of the contribution; it was not a stored-decision lookup. No per-item tool errors were recorded; the helper exited successfully. Raw normalized inputs, classification, explanation and server identity are preserved in request-guard-evidence.json.
Comparison with Cloudflare
The user supplied Cloudflare action
managed_challenge as context; it is not a field in the fixture and was not independently verified. Request Guard's
block verdict differs from that challenge action. These outputs come from different systems: the local verdict neither explains Cloudflare's action nor establishes that Cloudflare should block this event. No Cloudflare bot score or assessment was provided.
Limitations and next checks
This was a local stdio export assessment, with optional backends unconfigured. No Cloudflare connection was made, no real logs were fetched, and no security settings were changed. No live integration or AI Scraping Defense testing was performed. Nothing was published.
The user agent is self-declared; this match does not prove the caller used sqlmap or had malicious intent. The reported scraping category is the tool's classification, not independent attribution. One selected synthetic event cannot establish traffic prevalence, legitimacy, false-positive rate or challenge outcome. Headers, request body, response, timestamps, Cloudflare rule attribution, bot score and challenge outcome are absent.
For further investigation, obtain authorized sanitized rule attribution, bot assessment and challenge outcome separately, and compare a representative sample of legitimate and scanner-like metadata. Review any enforcement proposal separately; the helper's generated blocking recommendations were not executed.
Connects securely to your tools. The creator never sees your data.
About this skill
Map ClientRequestMethod, ClientRequestPath and ClientRequestUserAgent into local Request Guard assessments. Keep Cloudflare actions and bot assessments separate from the local classifier result. This is an export workflow, not a live Cloudflare API connector.
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
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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 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
Permissions
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.