{"repo":"useveto/node","free":true,"listed":false,"github":"https://github.com/useveto/node","clone":"git clone https://github.com/useveto/node.git","description":"Runtime authorization for AI agents — Node.js SDK","language":"TypeScript","stars":41,"topics":["agents","ai","authorization","mcp","security","typescript"],"license":"MIT","category":"auth-billing-email","readme_excerpt":"@useveto/node Runtime authorization for AI agents. The missing layer between identity and action. What is Veto? Veto intercepts every tool call your AI agent makes, evaluates it against your policies, and decides: allow , deny , or escalate . Sub-10ms. Default deny. - Default deny — no matching policy = blocked - MCP native — drop-in middleware for Model Context Protocol servers - Full audit trail — every decision logged - Edge-first — powered by Cloudflare Workers Install Quick Start MCP Integration Option 1: Guard wrapper (recommended) Wraps your tool handler — denied actions never execute. When denied, returns { content: [{ type: 'text', text: 'Authorization denied: ...' }], isError: true } . Option 2: Manual middleware Call at the start of your handler — throws VetoError if denied. API Reference VetoClient Authorization Agents Policies Audit Logs Error Handling Fail-Closed by Default If Veto is unreachable (network error, timeout), the SDK denies by default . You can override this: Links - Website: veto.tools - Dashboard: app.veto.tools - API Docs: docs.veto.tools - GitHub: github.com/useveto/node License MIT","default_branch":null,"files":null,"tree":[],"storefront":"/r/useveto","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/useveto/node/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}