Low Risk

get_dicom_export_job

get_dicom_export_job

How to control get_dicom_export_job ↓

What get_dicom_export_job does on Amazon EKS MCP Server

AI agents call get_dicom_export_job to retrieve information from Amazon EKS 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_dicom_export_job needs a policy

The 'get' prefix strongly suggests this is a retrieval/query operation with no side effects. However, confidence is moderate (0.65) because the description is empty, making it impossible to confirm the exact behavior. In an EKS context, this appears to be retrieving job metadata rather than executing operations. Classified as Read unless evidence emerges that it triggers job execution.

From the tool's definition Tool name 'get_dicom_export_job' uses the 'get' verb, indicating a retrieval operation. The name structure suggests querying the status or details of an existing DICOM export job rather than creating, modifying, or deleting resources.

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

How to control get_dicom_export_job

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

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

get_dicom_export_job 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 EKS 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_dicom_export_job

What does the get_dicom_export_job tool do? +

get_dicom_export_job. It is categorised as a Read tool in the Amazon EKS MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_dicom_export_job? +

Register the Amazon EKS MCP Server MCP server in PolicyLayer and add a rule for get_dicom_export_job: 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 EKS MCP Server. Nothing to install.

What risk level is get_dicom_export_job? +

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

Can I rate-limit get_dicom_export_job? +

Yes. Add a rate_limit block to the get_dicom_export_job 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_dicom_export_job completely? +

Set action: deny in the PolicyLayer policy for get_dicom_export_job. 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_dicom_export_job? +

get_dicom_export_job is provided by the Amazon EKS MCP Server MCP server (awslabs.eks-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 EKS MCP Server tool call.

Start from Amazon EKS 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 EKS 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.