Low Risk

list_dicom_import_jobs

list_dicom_import_jobs

How to control list_dicom_import_jobs ↓

What list_dicom_import_jobs does on Prometheus MCP Server

AI agents call list_dicom_import_jobs to retrieve information from Prometheus 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 list_dicom_import_jobs needs a policy

The 'list_' prefix strongly suggests this is a read-only operation that queries or enumerates existing DICOM import jobs. No indication of side effects, modifications, deletions, or external triggers. The empty description reduces confidence slightly, but the naming convention is a reliable signal for a Read category tool.

From the tool's definition Tool name 'list_dicom_import_jobs' indicates a listing/query operation with the 'list_' prefix, which retrieves data about DICOM import jobs without modifying state.

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

How to control list_dicom_import_jobs

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

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

list_dicom_import_jobs 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 Prometheus 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 list_dicom_import_jobs

What does the list_dicom_import_jobs tool do? +

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

How do I enforce a policy on list_dicom_import_jobs? +

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

What risk level is list_dicom_import_jobs? +

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

Can I rate-limit list_dicom_import_jobs? +

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

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

list_dicom_import_jobs is provided by the Prometheus MCP Server MCP server (awslabs.prometheus-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 Prometheus MCP Server tool call.

Start from Prometheus 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 Prometheus 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.