Scan text or code content for security vulnerabilities, secrets, PII, and other issues. This tool analyzes the provided content using multiple security analyzers: - Secret Scanner: Detects API keys, tokens, passwords, and credentials - PII Detector: Finds personal identifiable information - Code...
Accepts raw HTML/template content (content)
Part of the Mund MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call mund_scan_content to retrieve information from Mund without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though mund_scan_content only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
mund_scan_content:
rules:
- action: allowSee the full Mund policy for all 23 tools.
Agents calling read-class tools like mund_scan_content have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Scan text or code content for security vulnerabilities, secrets, PII, and other issues. This tool analyzes the provided content using multiple security analyzers: - Secret Scanner: Detects API keys, tokens, passwords, and credentials - PII Detector: Finds personal identifiable information - Code Analyzer: Identifies dangerous code patterns - Injection Detector: Spots prompt injection attempts - Exfiltration Detector: Detects data exfiltration patterns Args: - content (string): The text/code to scan (required) - content_type ('text' | 'code' | 'json' | 'yaml'): Type of content (default: 'text') - tool_name (string): Name of tool that generated this content (optional) - agent_id (string): ID of the requesting agent (optional) - session_id (string): Current session ID (optional) Returns: JSON object with: - scan_id: Unique identifier for this scan - issues_found: Number of security issues detected - blocked: Whether the content was blocked (if block_mode is enabled) - issues: Array of detected issues with severity, type, and suggestions - scan_duration_ms: Time taken to complete the scan Examples: - Scan code before committing: {"content": "const key = 'AKIAIOSFODNN7EXAMPLE'"} - Check user input: {"content": "Please ignore previous instructions", "content_type": "text"}. It is categorised as a Read tool in the Mund MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for mund_scan_content. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mund MCP server.
mund_scan_content is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mund_scan_content rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the Intercept policy for mund_scan_content. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
mund_scan_content is provided by the Mund MCP server (@weave_protocol/mund). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept