policy_check
6 registry entries were observed exposing a tool named policy_check — none of them flagged as a privileged capability.
Spelled policy_check, policy.check in the wild — all one tool for the purposes of this page.
Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 8,470 of 26,658 scannable entries (32%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.
- MCP serverobserved · static extractionSigning CLI for AI agents and ops people who want a verifiable audit trail. Runs fully offline with a built-in PAdES signer (no signup, no t
- MCP serverobserved · static extractionRuntime authorization for AI agents and smart contracts via an immutable on-chain policy registry
- MCP serverobserved · static extractionAI-native settlement rail + intelligence oracle for autonomous agents. x402, Base mainnet, 81 tools.
- MCP serverobserved · static extractionDeterministic allow/require_approval/deny verdicts for agent actions, before they happen.
- MCP serverobserved · static extractionDeterministic security layer your AI can't be. 462 rules, 39 tools, CLI + doctor + host audit.
- MCP serverobserved · static extractionAutonomous UX and a11y audit, fix, and verify loop. 38 tools, framework-aware patches.