AgentSentinel MCP Gateway
Related Servers
Alternatives to AgentSentinel MCP Gateway
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables autonomous agents to run shell and subprocess commands through a guardrail that blocks destructive system mutations, path traversals, and reverse shells. It also adds prompt-injection detection, spend circuit breakers, loop detection, and privacy sanitization so agent execution stays within safe, budgeted bounds.7MIT
- AlicenseAqualityBmaintenanceEnables agents to score, inspect, and gate tool calls before they execute, resolving shell commands the way a shell would in order to block destructive actions and detect multi-step attack sequences. It also redacts credentials and PII in either direction, requires signed single-use approval tokens for high-impact actions, and keeps a tamper-evident audit trail.670 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables autonomous agents to enforce financial guardrails by tracking real-time token burn and cost velocity, automatically throttling or freezing execution when budgets are exceeded. It also blocks destructive shell commands, prompt injections, and runaway planning loops while sanitizing outputs before they are returned.7MIT
- FlicenseAqualityBmaintenanceEnables AI agents to safely interact with GitHub, query Postgres read-only, check deployment status, and search/read files within an allowlisted sandbox—all with dry-run writes and SQL/path safety gates.8-
- AlicenseNot gradedqualityCmaintenanceEnables LLM agents to access third-party APIs through a least-privilege set of audited tools with allowlists, per-caller scopes, label gates, write confirmation, limits, and PII-masked logging. It restricts reads to labeled data, prevents sending or destructive actions, and records every allowed or denied call.MIT

agentguardofficial
AlicenseNot gradedqualityAmaintenanceEnforces policy controls for AI agents, including spend limits, action approvals, kill switch, scoped credentials, dry-run diffs, loop prevention, and auditable hash-chained logs.MIT
TDQS
Scored across 5 tools
Each tool targets a clearly distinct security capability: shell execution, filesystem operations, network fetching, policy pre-checking, and audit inspection. Although safe_exec could overlap with safe_fs or safe_fetch via shell commands, the sandbox descriptions make the intended boundaries clear.
All tools use snake_case with a consistent sentinel_ prefix, which is highly predictable. The pattern shifts slightly from sentinel_safe_<action> for operational tools to sentinel_<noun>_<verb> for policy and audit tools, but remains readable and coherent.
Five tools is well-scoped for a security gateway, covering execution, filesystem, network, policy, and audit without redundancy. Each tool earns its place in the minimal surface.
The core agent action surfaces are covered, plus policy evaluation and audit inspection. Minor gaps exist: safe_fs lacks explicit delete/remove, and there is no tool to manage policies or reset circuit breakers, but agents can likely work around these limitations.