Low Risk

mund_scan_content

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 ...

Risk signalsAccepts raw HTML/template content (content)

Part of the Mund server.

mund_scan_content is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE MUND →

Free to start. No card required.

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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "mund_scan_content": {}
  }
}

See the full Mund policy for all 23 tools.

Get this rule live on your own Mund server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MUND →

View all 23 tools →

These attack patterns abuse exactly the kind of access mund_scan_content gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so mund_scan_content only ever does what you allow.

SECURE MUND →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the mund_scan_content tool do? +

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.

How do I enforce a policy on mund_scan_content? +

Register the Mund MCP server in PolicyLayer and add a rule for mund_scan_content: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mund. Nothing to install.

What risk level is mund_scan_content? +

mund_scan_content is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mund_scan_content? +

Yes. Add a rate_limit block to the mund_scan_content rule in your PolicyLayer 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.

How do I block mund_scan_content completely? +

Set action: deny in the PolicyLayer 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.

What MCP server provides mund_scan_content? +

mund_scan_content is provided by the Mund MCP server (@weave_protocol/mund). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mund tool call.

Deterministic rules across all 23 Mund tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.