9 tools from the Vigile MCP Server, categorised by risk level.
View the Vigile policy →vigile_check_provenance Fetch canonical provenance payload for a memory source ID. vigile_check_server Look up the trust score and security findings for an MCP server in the Vigile registry. Returns trust score (0-100), trust level, findings summary,... vigile_check_skill Look up the trust score for an agent skill (claude.md, .cursorrules, skill.md, etc.) in the Vigile registry. Returns trust score, trust level, find... vigile_recall Recall prior Vigile security memory context for an entity, pattern, or incident. Returns compact context, evidence chunks, and source references wi... 2/5 vigile_scan_content Scan the content of an agent skill file for security issues. Submit raw content from a claude.md, .cursorrules, skill.md, or similar file for analy... vigile_search Search the Vigile registry for MCP servers and agent skills by keyword. Returns matching entries with trust scores. Use this when you need to find ... 2/5 vigile_timeline Fetch a security timeline for an incident or topic from Vigile memory. vigile_verify_location Assess location-related privacy and safety risks for AI agent interactions involving physical-world context (deliveries, meetups, financial transac... The Vigile MCP server exposes 9 tools across 2 categories: Read, Write.
Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Vigile server.
Vigile tools are categorised as Read (8), Write (1). Each category has a recommended default policy.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept