Loops HouseGuardian QA

NEAR HACKATHON
Links
Team
1 member- JOOwner
Jorge Rodriguez
Overview
Guardian QA is a pre-execution counterparty check and policy gate for AI payment agents, shipped as a Python MCP server (guardian-qa-mcp).
Agents are getting wallets, and a prompt-injected page can make one pay an attacker before a human sees the transaction. Guardian QA sits between the intent and the signature. It checks destination account age and activity, prior interactions, stablecoin contract and network validity, a shared blocklist with evidence reporting, and prompt injection in the text that produced the payment (local heuristics plus a NEAR AI Cloud classifier). It returns exactly allow, warn or block, with structured reason codes and an explanation. The agent wrapper refuses and logs on block, halts for explicit human approval on warn, and proceeds in dry-run on allow. A red-team suite of 19 abliterated-model-generated attacks was contained 19/19 with 0 escapes; a GPT-4.1-mini victim complied with 18 of 19 injected destinations and every compliant attempt was blocked or warned.
NEAR fits end to end: read-only NEAR testnet RPC and NearBlocks signals, MCP tools any NEAR agent stack can call, and NEAR AI Cloud for the injection classifier, the abliterated attacker and TEE evidence recording. It is a least-privilege runtime check analogous to a function-call key, with its limits documented. No mainnet, no real funds, no private keys.