site_crawl
Crawl a website starting from a URL (same-site BFS, form-heavy pages prioritised).
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/site-crawl.md
What site_crawl does on Samarth Gtm Mcp
AI agents invoke site_crawl to trigger actions in Samarth Gtm 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 site_crawl is rated High
Crawling a website involves actively sending HTTP requests to external URLs, performing breadth-first traversal, and interacting with pages (prioritising form-heavy pages implies potential form interaction). This is an external operation whose scope and side effects depend on the arguments provided.
From the tool's definition Crawl a website starting from a URL (same-site BFS, form-heavy pages prioritised)
Attacks that exploit this kind of access
The rule that runs site_crawl safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Samarth Gtm Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For site_crawl, this is the rule to start with:
site_crawl 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Samarth Gtm Mcp, apply this rule, and every site_crawl call is checked against it from then on.
Questions about site_crawl
Crawl a website starting from a URL (same-site BFS, form-heavy pages prioritised). It is categorised as a Execute tool in the Samarth Gtm Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Samarth Gtm MCP server in PolicyLayer and add a rule for site_crawl: 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 Samarth Gtm Mcp. Nothing to install.
site_crawl is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the site_crawl 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.
Set action: deny in the PolicyLayer policy for site_crawl. 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.
site_crawl is provided by the Samarth Gtm MCP server (samarth-gtm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Samarth Gtm, and thousands of servers like it.
Across the catalogue