Get detailed information about a specific HealthLake datastore
AI agents call get_datastore_details 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.
This tool retrieves information about a HealthLake datastore. The verb 'Get' and the read-only nature of fetching 'detailed information' classify it as a Read operation. There are no side effects, no data modification, and no external operations triggered.
From the tool's definition Tool name 'get_datastore_details' and description 'Get detailed information about a specific HealthLake datastore' indicate retrieval of datastore metadata without modification or deletion.
Attacks that exploit this kind of access
Get detailed information about a specific HealthLake datastore. 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_datastore_details: 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_datastore_details 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_datastore_details 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_datastore_details. 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_datastore_details 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.