Search curated AgentCore documentation and return ranked results with snippets. This tool provides access to the complete Amazon Bedrock AgentCore documentation including: **Platform Overview:** - What is Bedrock AgentCore, security overview, quotas and limits **Platform Services:** - AgentCor...
Accepts freeform code/query input (query)
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 search_agentcore_docs 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 search_agentcore_docs 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:
search_agentcore_docs:
rules:
- action: allow See the full AWS Bedrock AgentCore MCP Server policy for all 122 tools.
Agents calling read-class tools like search_agentcore_docs 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.
Search curated AgentCore documentation and return ranked results with snippets. This tool provides access to the complete Amazon Bedrock AgentCore documentation including: **Platform Overview:** - What is Bedrock AgentCore, security overview, quotas and limits **Platform Services:** - AgentCore Runtime (serverless deployment and scaling) - AgentCore Memory (persistent knowledge with event and semantic memory) - AgentCore Code Interpreter (secure code execution in isolated sandboxes) - AgentCore Browser (fast, secure cloud-based browser for web interaction) - AgentCore Gateway (transform existing APIs into agent tools) - AgentCore Observability (real-time monitoring and tracing) - AgentCore Identity (secure authentication and access management) **Getting Started:** - Prerequisites & environment setup - Building your first agent or transforming existing code - Local development & testing - Deployment to AgentCore using CLI - Troubleshooting & enhancement **Examples & Tutorials:** - Basic agent creation, memory integration, tool usage - Streaming responses, error handling, authentication - Customer service agents, code review assistants, data analysis - Multi-agent workflows and integrations **API Reference:** - Data plane and control API documentation Use this to find relevant AgentCore documentation for any development question. Args: query: Search query string (e.g., "bedrock agentcore", "memory integration", "deployment guide") k: Maximum number of results to return (default: 5) Returns: List of dictionaries containing: - url: Document URL - title: Display title - score: Relevance score (0-1, higher is better) - snippet: Contextual content preview. 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 search_agentcore_docs. 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.
search_agentcore_docs 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 search_agentcore_docs 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 search_agentcore_docs. 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.
search_agentcore_docs 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.