get_metric_metadata
AI agents call get_metric_metadata 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 name strongly suggests it retrieves or queries metric metadata from SageMaker, which is a read-only operation with no side effects. However, confidence is moderate (0.75) rather than high because the description is empty, preventing confirmation of the exact data returned, access controls, or whether any sensitive information exposure could elevate risk.
From the tool's definition Tool name 'get_metric_metadata' indicates retrieval of metadata about metrics. The verb 'get' is a standard read operation that queries or retrieves information without modification.
Attacks that exploit this kind of access
get_metric_metadata. 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_metric_metadata: 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_metric_metadata 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_metric_metadata 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_metric_metadata. 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_metric_metadata 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.