TraceGuard Core
Related Servers
Alternatives to TraceGuard Core
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides an MCP stdio interface for AI agents to propose tool calls that are validated against task policy, held for human approval when required, executed in a sandboxed Linux environment, and recorded in an audit log.MIT
- AlicenseNot gradedqualityBmaintenanceWraps any stdio MCP server, holding each tool call until a human approves or denies it from their phone, and only then executing the call.MIT
- AlicenseNot gradedqualityCmaintenanceA transparent MCP stdio proxy that sits between an agent client and a real MCP server, intercepting tools/call requests to enforce runtime guardrails derived from the same YAML rules used for CI regression testing. It blocks forbidden, out-of-whitelist, looping, or non-idempotent tool invocations with JSON-RPC errors and writes every decision to an audit log.1MIT
- AlicenseNot gradedqualityCmaintenanceSits in front of any MCP server to enforce allow/ask/block policies on tool calls, paths, shell commands, and network domains, with local approval prompts and an audit log.MIT
- AlicenseBqualityAmaintenanceProvenance gateway for stdio MCP servers. Runs in front of any MCP server, drafts a policy per tool from the server's own schemas, and blocks a tools/call whose destination or content came from an untrusted tool result, regardless of wording. The blocked call is returned as an error result with the provenance chain. Python, Apache-2.0, pip install reasongate.81428 PyPI16Apache 2.0
- AlicenseAqualityDmaintenanceExposes a verified tool registry (calculator, sandboxed file read, web fetch) over MCP stdio, enabling any MCP-capable client to reuse the same tools from the inspectable ReAct loop.3MIT
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusion or overlap with another tool. The tool's purpose is clearly stated as an allow/block check for exact action names.
The single tool name `traceguard_check_action` follows a clear verb_noun snake_case pattern with a consistent prefix. There are no other names to conflict with, so consistency is trivially perfect.
A server named 'TraceGuard Core' with only one tool feels too thin for its apparent scope of policy enforcement. The tool itself is substantive, but a core authorization service typically requires more operations (e.g., managing the allowlist, listing allowed actions).
The surface only checks actions against a pre-configured allowlist. There is no way to inspect or modify the allowlist, validate arguments, or execute actions, leaving significant gaps for a policy server. Agents cannot manage or audit the policy through this server.