connect
AI agents call connect as a supporting operation in Amazon SageMaker AI MCP Server workflows.
The description is empty and uninformative, making it impossible to determine the tool's actual behavior. The name 'connect' alone could refer to establishing a connection/session (likely Read or Execute), but without evidence, confidence is very low. Defaulting to Other with low severity.
From the tool's definition Tool name is 'connect' with an empty description. No information about what this tool does is provided.
Attacks that exploit this kind of access
connect. It is categorised as a Other tool in the Amazon SageMaker AI MCP Server MCP Server, which means it performs auxiliary operations.
Register the Amazon SageMaker AI MCP Server MCP server in PolicyLayer and add a rule for connect: 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.
connect is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the connect 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 connect. 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.
connect 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.