DEPENDENCY MAPPING TOOL - Analyze dependencies within and across groups. Use this tool when users ask: - "What are the dependencies of the Payment group?" - "What does the checkout application depend on?" - "What external services does the Checkout group use?" - "Show me the dependency map for t...
Part of the CloudWatch Application Signals MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_group_dependencies to retrieve information from CloudWatch Application Signals 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 get_group_dependencies 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:
get_group_dependencies:
rules:
- action: allowSee the full CloudWatch Application Signals MCP Server policy for all 22 tools.
Agents calling read-class tools like get_group_dependencies 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.
DEPENDENCY MAPPING TOOL - Analyze dependencies within and across groups. Use this tool when users ask: - "What are the dependencies of the Payment group?" - "What does the checkout application depend on?" - "What external services does the Checkout group use?" - "Show me the dependency map for the API group" **WHAT THIS TOOL DOES:** Maps all dependencies for services in a group: - Intra-group: Dependencies between services within the same group - Cross-group: Dependencies on services in other groups - External: Dependencies on AWS services (S3, DynamoDB, SQS, etc.) **OUTPUT INCLUDES:** - Intra-group dependency graph - Cross-group dependencies - External AWS service dependencies **EXAMPLES:** ``` get_group_dependencies(group_name='Payments') get_group_dependencies(group_name='*api*') ```. It is categorised as a Read tool in the CloudWatch Application Signals 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 get_group_dependencies. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the CloudWatch Application Signals MCP Server MCP server.
get_group_dependencies 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_group_dependencies 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 get_group_dependencies. 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_group_dependencies is provided by the CloudWatch Application Signals MCP Server MCP server (awslabs.cloudwatch-applicationsignals-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.