update_agent_runtime_endpoint
AI agents use update_agent_runtime_endpoint to create or update resources in Amazon SageMaker AI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Amazon SageMaker AI MCP Server environment.
The 'update_' prefix strongly suggests a write/modify operation, likely updating an agent runtime endpoint configuration in SageMaker. This could affect running inference endpoints. Description is empty, so confidence is reduced. Severity is high because modifying a runtime endpoint could disrupt production ML workloads.
From the tool's definition Tool name: update_agent_runtime_endpoint — description is empty/uninformative
Attacks that exploit this kind of access
update_agent_runtime_endpoint. It is categorised as a Write tool in the Amazon SageMaker AI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Amazon SageMaker AI MCP Server MCP server in PolicyLayer and add a rule for update_agent_runtime_endpoint: 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.
update_agent_runtime_endpoint is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_agent_runtime_endpoint 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 update_agent_runtime_endpoint. 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.
update_agent_runtime_endpoint 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.