Fetch full document content by URL. Retrieves complete AgentCore documentation content from URLs found via search_agentcore_docs or provided directly. Use this to get full documentation pages including: - Complete platform overview and service documentation - Detailed getting started guides wit...
Accepts URL/endpoint input (uri)
Part of the AWS Bedrock AgentCore MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call fetch_agentcore_doc to retrieve information from AWS Bedrock AgentCore MCP Server 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 fetch_agentcore_doc 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:
fetch_agentcore_doc:
rules:
- action: allowSee the full AWS Bedrock AgentCore MCP Server policy for all 122 tools.
Agents calling read-class tools like fetch_agentcore_doc 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.
Fetch full document content by URL. Retrieves complete AgentCore documentation content from URLs found via search_agentcore_docs or provided directly. Use this to get full documentation pages including: - Complete platform overview and service documentation - Detailed getting started guides with step-by-step instructions - Full API reference documentation - Comprehensive tutorial and example code - Complete deployment and configuration instructions - Integration guides for various frameworks (Strands, LangGraph, CrewAI, etc.) This provides the full content when search snippets aren't sufficient for understanding or implementing AgentCore features. Args: uri: Document URI (supports http/https URLs) Returns: Dictionary containing: - url: Canonical document URL - title: Document title - content: Full document text content - error: Error message (if fetch failed). It is categorised as a Read tool in the AWS Bedrock AgentCore MCP Server MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for fetch_agentcore_doc. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS Bedrock AgentCore MCP Server MCP server.
fetch_agentcore_doc 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 fetch_agentcore_doc 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 fetch_agentcore_doc. 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.
fetch_agentcore_doc is provided by the AWS Bedrock AgentCore MCP Server MCP server (awslabs.amazon-bedrock-agentcore-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.