Get architecture patterns for Amazon Bedrock applications, including component relationships and cost considerations
AI agents call get_bedrock_patterns to retrieve information from Amazon Data Processing MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries pre-existing architecture pattern information from Amazon Bedrock. The verb 'Get' and the nature of the operation (fetching documentation or reference patterns) classify this as a Read operation. There are no side effects, no code execution, no data modification, and no destructive actions. The blast radius of misuse is minimal—an agent could only retrieve architectural documentation.
From the tool's definition Tool description states 'Get architecture patterns' which is a retrieval operation. The description explicitly indicates data querying (architecture patterns, component relationships, cost considerations) with no modification or execution capability mentioned.
Documented attack patterns abuse exactly the kind of access get_bedrock_patterns gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Data Processing MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_bedrock_patterns:
{
"version": "1",
"default": "deny",
"tools": {
"get_bedrock_patterns": {}
}
} get_bedrock_patterns is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get architecture patterns for Amazon Bedrock applications, including component relationships and cost considerations. It is categorised as a Read tool in the Amazon Data Processing MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amazon Data Processing MCP Server MCP server in PolicyLayer and add a rule for get_bedrock_patterns: 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 Amazon Data Processing MCP Server. Nothing to install.
get_bedrock_patterns 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 get_bedrock_patterns 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 get_bedrock_patterns. 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.
get_bedrock_patterns is provided by the Amazon Data Processing MCP Server MCP server (awslabs.aws-dataprocessing-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon Data Processing MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 Amazon Data Processing MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.