Deterministic preflight checks for credentials, fund transfers, writes, and prompt overrides.
Scored across 2 tools
The two tools have clearly distinct purposes: one assesses action risk, the other describes the guardrail's capabilities. There is no overlap or ambiguity between them.
Both tools use a consistent verb_noun pattern: 'assess_action_risk' and 'get_guardrail_capabilities'. The naming is predictable and follows a clear convention.
With only two tools, the server feels thin even for a narrowly scoped guardrail checker. The count is borderline, but the limited purpose partially justifies it.
The core workflow of checking capabilities and assessing risk is covered. Minor gaps exist, such as no explicit way to list individual guardrail rules, but the surface is not a dead end.
Runs a deterministic, read-only preflight check. It never executes the proposed action.
Inputs: action (required), content.
Returns the scope and safety boundary of this free, deterministic preflight checker.
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Stop your agent before it runs rm -rf /etc or emails your .env. Deterministic preflight checks.
Independent agent preflight: verify change, mandates, evidence, and exact execution.
Risk preflight for AI Agent tool actions and Polymarket settlement and execution checks.
Advisory policy preflight for AI-agent spend requests; never executes payments or accesses wallets.
Add one secure layer between your agents and this server.