fetch-apify-docs
on npm:@apify/actors-mcp-server@0.10.11
Severity
3 findings on this tool
- highssrf surfacef-r8-fetch_apify_docs
Tool `fetch-apify-docs` accepts an unconstrained URL / endpoint parameter
The parameter(s) `url` look like URL or endpoint inputs but carry no `pattern` or `enum` constraint. An agent tricked by an indirect-injection payload can invoke this tool with an internal-service URL (e.g. `http://169.254.169.254/`) to exfiltrate cloud metadata, probe internal APIs, or pivot to services the host can reach but the caller cannot.
fix: Constrain the URL parameter with an allow-list `enum`, or a `pattern` that restricts scheme and domain. Validate server-side against an allow-list and reject private / loopback / link-local address ranges at the HTTP client level.
OWASP LLM07NIST MANAGE-2.2ATLAS T0051CAST-02 - mediumunconstrained inputf-r1-fetch_apify_docs
Tool `fetch-apify-docs` accepts unconstrained string input
The following string parameter(s) have no `maxLength` constraint: `url`. Unbounded strings let an attacker stuff arbitrary payloads through the tool, including indirect-injection content.
fix: Add a `maxLength` to each string property, or constrain with an `enum` or `pattern`. Most legitimate tool inputs fit under a few hundred bytes.
OWASP LLM01NIST MEASURE-2.3ATLAS T0051CAST-03 - mediumindirect injectionf-r6-fetch_apify_docs
Tool `fetch-apify-docs` fetches external web content -- indirect-injection surface
Description: "Fetch the full content of an Apify or Crawlee documentation page by its URL. Use this after finding a relevant page with the search-apify-docs tool. USAGE: - Use when you need the complete content of a specific docs page for detailed answers. USAGE EXAMPLES: - user_input: Fetch https://docs.apify.com/platform/actors/running#builds - user_input: Fetch https://docs.apify.com/academy - user_input: Fetch https://crawlee.dev/docs/guides/basic-concepts" -- this tool pulls externally-controlled content into the agent's context window, the canonical indirect-injection vector. Even when the user supplies the URL, content at that URL can carry hostile instructions.
fix: Sandbox the fetched content: strip prompts before forwarding to the model, constrain to an allow-list of domains, and route through capframe-guard with a `domain in [...]` caveat.
OWASP LLM01NIST MEASURE-2.3ATLAS T0051CAST-02
About this tool
fetch-apify-docs is one of 9 tools exposed by Apify Actors MCP. The server scored 64/100 overall against the capframe rule engine (source: sandbox). Last scanned 2026-07-20.
The findings above are emitted by the public capframe.findings.v1 schema. Disagree with one? Open an issue.