search_places
AI agents call search_places 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.
Search operations typically retrieve data without side effects, fitting the Read category. The empty description reduces confidence, but the verb 'search' strongly suggests a read-only query operation. Low severity assigned because search tools have minimal blast radius—worst case is information disclosure of place data.
From the tool's definition Tool name 'search_places' indicates a search/query operation. Description is empty, limiting definitive classification.
Attacks that exploit this kind of access
search_places. 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 search_places: 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.
search_places 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 search_places 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 search_places. 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.
search_places 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.