get_dashboard_summary
AI agents call get_dashboard_summary to retrieve information from AWS_CloudGuardMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the name and sibling tools that are clearly read-only (list_cloudwatch_dashboards, fetch_cloudwatch_logs_for_service, get_cloudwatch_alarms_for_service), this tool appears to retrieve dashboard summary information without modifying it.
From the tool's definition Tool name 'get_dashboard_summary' and server context 'list_cloudwatch_dashboards' and 'analyze_log_group' suggest this retrieves CloudWatch dashboard data. Description is empty, limiting confidence.
Attacks that exploit this kind of access
get_dashboard_summary. It is categorised as a Read tool in the AWS_CloudGuardMCP MCP Server, which means it retrieves data without modifying state.
Register the AWS_CloudGuard MCP server in PolicyLayer and add a rule for get_dashboard_summary: 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 AWS_CloudGuardMCP. Nothing to install.
get_dashboard_summary 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_dashboard_summary 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_dashboard_summary. 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_dashboard_summary is provided by the AWS_CloudGuard MCP server (madhurprash/aws_cloudguardmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →