Get concept details by ID
AI agents call get_concept to retrieve information from SNOMED CT 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 and returns concept details from SNOMED CT terminology by ID lookup. It performs a read-only query with no side effects, no code execution, no data modification, and no destructive operations. The blast radius is minimal—it only returns pre-existing medical terminology information. Confidence is high based on clear read semantics in both name and description.
From the tool's definition Tool name 'get_concept' and description 'Get concept details by ID' indicate retrieval of existing data with no modification.
Attacks that exploit this kind of access
Get concept details by ID. It is categorised as a Read tool in the SNOMED CT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SNOMED CT MCP Server MCP server in PolicyLayer and add a rule for get_concept: 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 SNOMED CT MCP Server. Nothing to install.
get_concept 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_concept 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_concept. 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_concept is provided by the SNOMED CT MCP Server MCP server (orglance/snomed-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_concept is one line of SNOMED CT MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →