mcpField
T
ToolOracle — AI Agent Tool Infrastructure & Trust Runtime

ToolOracle — AI Agent Tool Infrastructure & Trust Runtime

Remote
github.com/ToolOracleAI & Agents0Updated 29w ago
Repository

About ToolOracle — AI Agent Tool Infrastructure & Trust Runtime

AgentGuard is a governance and security MCP server for AI agent tool execution, aimed at regulated workflows and autonomous payments. It combines policy checks, threat scanning, approval gates, and signed audit records.

Key features

  1. 01Preflight policy decisions and risk scores
  2. 02Secret and injection detection
  3. 03Payment limits and approval checks
  4. 04Role, session, and tenant controls
  5. 05Signed, queryable audit trail

Use cases

  1. 01Gate autonomous payment tool calls
  2. 02Review agent activity for compliance
  3. 03Scan tool inputs for secrets or injection

MCP support

Exposes security, policy, payment-control, threat-analysis, and audit tools to MCP clients. It can be connected through the FeedOracle or ToolOracle MCP endpoints.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://feedoracle.io/guard-oracle/mcp/
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

13
ParameterTypeRequiredDescription
keywordstringNoSeed keyword to research
countrystringNoCountry code (DE, US, UK, AT, CH, etc.)

Details

From the project README

🛡️ AgentGuard MCP

Security, Policy & Audit Layer for AI Agent Tool Execution — 20 tools | Part of FeedOracle & ToolOracle

Tools Status Backend Tier

AgentGuard is the governance and security layer for AI agent workflows. Before any tool executes, AgentGuard evaluates policies, scores risk, detects secrets and injection attempts, logs to a tamper-evident audit trail, and explains every decision. Built for regulated environments, autonomous payments, and enterprise AI agent deployments.

Quick Connect

# FeedOracle (compliance-focused)
npx -y mcp-remote https://feedoracle.io/guard/mcp/

# ToolOracle (agent-commerce focused)
npx -y mcp-remote https://tooloracle.io/guard/mcp/
{
  "mcpServers": {
    "agentguard": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://feedoracle.io/guard/mcp/"]
    }
  }
}

How It Works — The Agent Security Loop

Agent wants to call: payment_execute({amount: 5000})
         │
         ▼
   policy_preflight()         ← Check before execution
         │
   risk_score: 95             ← Critical
   matched: pol-001, pol-002  ← Payment + High-risk policies
   decision: require_approval ← Human gate triggered
         │
   approval_required()        ← Register pending approval
         │
   [Human approves]
         │
   tool executes
         │
   audit_log_write()          ← Record outcome with signature
         │
   decision_explain()         ← Exportable compliance evidence

Tools — Welle 1: Core Security (7)

ToolDescription
policy_preflightPre-flight check before any tool call. Evaluates 7 policies, computes risk score, detects threats, auto-logs. Returns allowed/denied/require_approval/flagged.
tool_risk_score0-100 risk score for tool + input. Detects secrets (API keys, passwords), prompt injection, high-value amounts. eth_gas→5, payment_execute→95+.
approval_requiredCheck if tool needs human approval. Optionally registers a pending approval request with tracking URL.
audit_log_writeWrite tool execution to persistent, cryptographically-signed audit log (SQLite WAL). Call after execution to record outcome.
audit_log_queryQuery audit trail. Filter by agent, tool, decision, time range. Paginated. Returns signed entries for tamper verification.
decision_explainHuman-readable explanation of any allow/deny decision. Pass request_id for stored entry or tool_name + tool_args for fresh analysis.
rate_limit_checkCheck agent rate limits: 200/min, 5000/hr, 50000/day. Returns per-window usage with percentage.

Tools — Welle 2: Payment Controls & Safety

ToolDescription
payment_policy_checkValidate payment against policy: amount limits (>100k warns, >1M blocks), recipient denylist, supported currencies/networks, AML thresholds (>10k fiat flagged), MiCA flags.
spend_limit_checkCheck per-call/hour/day spend limits by trust level. Default: 10k/call, 50k/hr, 200k/day. Trusted: 100k/call, 500k/hr, 2M/day.
secret_exposure_checkDeep scan for 19 secret patterns: OpenAI/GitHub/AWS/Slack keys, Bearer/Basic auth, ETH private keys, Bitcoin WIF, credit cards, SSNs, emails. Returns severity + remediation.
payload_safety_check18-pattern safety scan: prompt injection, jailbreak/DAN, role hijacking, SQL (UNION/DROP/OR 1=1), XSS, Python/JS/Shell injection, path traversal, null bytes, oversized payloads.
replay_guard_checkDetect replay attacks via SHA256 fingerprint (agent+tool+args). Configurable window (default 5 min). Returns duplicate count + first/last seen.

Tools — Welle 3: Governance & Threat Intelligence (5)

ToolDescription
cross_tool_anomaly_checkDetect anomalous patterns: risky combos (wallet-recon→transfer, AML→payment), high frequency, repeated denials (policy probing), broad reconnaissance, elevated avg risk score.
scope_checkRole-based scope control. Roles: admin, compliance_officer, trader, auditor, developer, readonly. Returns has_scope, missing scope, granting roles. Logs denials.
session_validateFull session lifecycle: create (TTL + call budget), validate (increment counter), invalidate, info. Sessions carry role, scopes, tenant, expiry.
tenant_policy_checkMulti-tenant governance. Built-in tenants: default, fintech_eu (MiCA/DORA/AMLD6), defi_protocol, enterprise_read. Per-tenant blocklists, risk limits, spend caps.
threat_intel_checkEntity threat intelligence. Auto-detects ETH addresses, IPs, domains. Checks sanctions (Tornado Cash, mixers), disposable services, behavioral analysis from audit log.
Built-in Tenants
TenantMax RiskSpend/DayFrameworks
default70100,000—
fintech_eu60500,000MiCA, DORA, AMLD6
defi_protocol8010,000,000MiCA
enterprise_read300—
Built-in Roles & Scopes
RoleScopes
adminAll scopes
compliance_officeraudit:read, compliance:read, blockchain:read, security:scan
traderblockchain:read, payment:check, payment:execute, audit:read
auditoraudit:read, audit:write, compliance:read, monitor:read
developerblockchain:read, security:scan, audit:read, monitor:read
readonlyblockchain:read, audit:read

Built-in Policies (7 Default)

PolicyConditionAction
pol-001Payment/transfer toolsrequire_approval
pol-002Risk score ≥ 80require_approval
pol-003Secret/key in payloaddeny
pol-004Rate limit exceededflag
pol-005Risk score ≤ 20allow freely
pol-006Prompt injection detecteddeny
pol-007Same tool > 50 calls/60sflag

Risk Score Guide

ScoreLevelAction
0-14MinimalProceed freely
15-39LowProceed, log for audit
40-69MediumFlag and proceed with caution
70-89HighRequire human approval
90-100CriticalBlock execution

Use Cases

  • Regulated AI Workflows: MiCA/DORA compliance requires audit trails — AgentGuard provides them automatically
  • Autonomous Payments: x402 agent payments run through approval_required gate before execution
  • Multi-tenant Platforms: Rate limiting and policy scoping per agent/session
  • Security Monitoring: Real-time detection of prompt injection and secret exposure in tool arguments
  • Compliance Reporting: Export audit log with cryptographic signatures for regulatory review

Backend: SQLite WAL-Mode

Persistent, stable, no daemon required. WAL-mode supports 1000+ writes/second. Shared between feedoracle.io and tooloracle.io — one source of truth.

Links

  • 🛡️ FeedOracle: https://feedoracle.io/guard/mcp/
  • 🔧 ToolOracle: https://tooloracle.io/guard/mcp/
  • 📚 Docs: feedoracle.io
  • 🏠 Platform: tooloracle.io

Built by FeedOracle — Evidence by Design

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.