Low Risk

get_datastore_details

Get detailed information about a specific HealthLake datastore

How to control get_datastore_details ↓

What get_datastore_details does on Amazon Data Processing MCP Server

AI agents call get_datastore_details to retrieve information from Amazon Data Processing MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_datastore_details needs a policy

The tool retrieves and queries information about an existing HealthLake datastore. This is a read-only operation with no side effects, no data modification, and no irreversible actions. The blast radius of misuse is limited to information disclosure.

From the tool's definition Tool name 'get_datastore_details' and description 'Get detailed information about a specific HealthLake datastore' indicate a retrieval operation with no modification, deletion, or execution of external operations.

Documented attack patterns abuse exactly the kind of access get_datastore_details gives an agent:

How to control get_datastore_details

PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Data Processing MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_datastore_details:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_datastore_details": {}
  }
}

get_datastore_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Amazon Data Processing MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_datastore_details

What does the get_datastore_details tool do? +

Get detailed information about a specific HealthLake datastore. It is categorised as a Read tool in the Amazon Data Processing MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_datastore_details? +

Register the Amazon Data Processing 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 Data Processing MCP Server. Nothing to install.

What risk level is get_datastore_details? +

get_datastore_details is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_datastore_details? +

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.

How do I block get_datastore_details completely? +

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.

What MCP server provides get_datastore_details? +

get_datastore_details is provided by the Amazon Data Processing MCP Server MCP server (awslabs.aws-dataprocessing-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Amazon Data Processing MCP Server tool call.

Start from Amazon Data Processing MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

805 Amazon Data Processing MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.