indexfoundry_connect_sitemap · IndexFoundry MCP

WHAT IT DOES

What indexfoundry_connect_sitemap does on IndexFoundry MCP

AI agents invoke indexfoundry_connect_sitemap to trigger actions in IndexFoundry MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why indexfoundry_connect_sitemap needs a policy

This tool actively crawls external URLs and fetches web pages, triggering outbound network operations whose scope and impact depend on the sitemap contents and filter arguments. This goes beyond passive reading — it executes a crawling process against potentially many external resources concurrently, qualifying it as Execute rather than Read.

From the tool's definition Crawl a sitemap XML file and fetch all linked pages. Supports URL pattern filtering, concurrent fetching, and depth limits.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

indexfoundry_connect_sitemap Rate-limited

indexfoundry_connect_sitemap stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "indexfoundry_connect_sitemap": {
      "limits": [
        {
          "counter": "indexfoundry_connect_sitemap_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches IndexFoundry MCP, so you can run agents against it safely.

FAQ

Questions about indexfoundry_connect_sitemap

What does the indexfoundry_connect_sitemap tool do? +

Crawl a sitemap XML file and fetch all linked pages. Supports URL pattern filtering, concurrent fetching, and depth limits. It is categorised as a Execute tool in the IndexFoundry MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on indexfoundry_connect_sitemap? +

Register the IndexFoundry MCP server in PolicyLayer and add a rule for indexfoundry_connect_sitemap: 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 IndexFoundry MCP. Nothing to install.

What risk level is indexfoundry_connect_sitemap? +

indexfoundry_connect_sitemap is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit indexfoundry_connect_sitemap? +

Yes. Add a rate_limit block to the indexfoundry_connect_sitemap 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 indexfoundry_connect_sitemap completely? +

Set action: deny in the PolicyLayer policy for indexfoundry_connect_sitemap. 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 indexfoundry_connect_sitemap? +

indexfoundry_connect_sitemap is provided by the IndexFoundry MCP server (mnehmos/mnehmos.index-foundry.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.