Retrieve security services data that was stored in context from a previous CheckSecurityServices call. This tool allows you to access security service status data stored by the CheckSecurityServices tool without making additional AWS API calls. This is useful for workflows where you need to refe...
Part of the AWS Well-Architected Security Assessment Tool MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call GetStoredSecurityContext to retrieve information from AWS Well-Architected Security Assessment Tool 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 GetStoredSecurityContext 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:
GetStoredSecurityContext:
rules:
- action: allowSee the full AWS Well-Architected Security Assessment Tool MCP Server policy for all 6 tools.
Agents calling read-class tools like GetStoredSecurityContext 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.
Retrieve security services data that was stored in context from a previous CheckSecurityServices call. This tool allows you to access security service status data stored by the CheckSecurityServices tool without making additional AWS API calls. This is useful for workflows where you need to reference the security services status in subsequent steps. ## Response format Returns a dictionary with: - region: The region the data was stored for - available: Boolean indicating if data is available for the requested region - data: The stored security services data (if available and detailed=True) - summary: A summary of the stored data (if available) - timestamp: When the data was stored (if available) ## Note This tool requires that CheckSecurityServices was previously called with store_in_context=True for the requested region.. It is categorised as a Read tool in the AWS Well-Architected Security Assessment Tool 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 GetStoredSecurityContext. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS Well-Architected Security Assessment Tool MCP Server MCP server.
GetStoredSecurityContext 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 GetStoredSecurityContext 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 GetStoredSecurityContext. 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.
GetStoredSecurityContext is provided by the AWS Well-Architected Security Assessment Tool MCP Server MCP server (awslabs.well-architected-security-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.