get_cloudwatch_logs
AI agents call get_cloudwatch_logs to retrieve information from Amazon SageMaker AI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves logs from CloudWatch for viewing and analysis purposes. Even without a detailed description, 'get' combined with 'logs' indicates a read operation that queries existing data without modification, deletion, or execution of code. The blast radius is minimal since it only exposes previously recorded logs for inspection.
From the tool's definition Tool name 'get_cloudwatch_logs' indicates retrieval of CloudWatch logs; description is empty but the verb 'get' and context of CloudWatch logs (a logging/monitoring service) strongly suggest read-only data retrieval.
Attacks that exploit this kind of access
get_cloudwatch_logs. It is categorised as a Read tool in the Amazon SageMaker AI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amazon SageMaker AI MCP Server MCP server in PolicyLayer and add a rule for get_cloudwatch_logs: 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 SageMaker AI MCP Server. Nothing to install.
get_cloudwatch_logs 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_cloudwatch_logs 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_cloudwatch_logs. 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_cloudwatch_logs is provided by the Amazon SageMaker AI MCP Server MCP server (awslabs.sagemaker-ai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.