get_attribute_presets
AI agents call get_attribute_presets to retrieve information from Simple Dicom without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name indicates fetching preset attributes or configurations from a DICOM server, which is a read operation with no side effects. While the description is empty, the context of a read-focused DICOM query server and naming pattern consistent with retrieval operations strongly suggests this is a simple data-retrieval tool.
From the tool's definition Tool name 'get_attribute_presets' suggests retrieving preset configurations; the server context is 'query and read data on DICOM servers'; sibling tools (list_dicom_nodes, query_instances, query_patients, query_series, query_studies) are all read-only…
Attacks that exploit this kind of access
get_attribute_presets. It is categorised as a Read tool in the Simple Dicom MCP Server, which means it retrieves data without modifying state.
Register the Simple Dicom MCP server in PolicyLayer and add a rule for get_attribute_presets: 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 Simple Dicom. Nothing to install.
get_attribute_presets 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_attribute_presets 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_attribute_presets. 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_attribute_presets is provided by the Simple Dicom MCP server (thalesmms/simple-dicom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →