Low Risk

get_concept

Get detailed information about a specific OMOP concept by its numeric concept_id. Returns the concept name, vocabulary, domain, concept class, standard status, valid dates, and synonyms. Use this when you already have a concept_id and need its details.

Part of the Omophub server.

get_concept is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE OMOPHUB →

Free to start. No card required.

AI agents call get_concept to retrieve information from Omophub without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_concept only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

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

See the full Omophub policy for all 11 tools.

Get this rule live on your own Omophub server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY OMOPHUB →

View all 11 tools →

These attack patterns abuse exactly the kind of access get_concept gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so get_concept only ever does what you allow.

SECURE OMOPHUB →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the get_concept tool do? +

Get detailed information about a specific OMOP concept by its numeric concept_id. Returns the concept name, vocabulary, domain, concept class, standard status, valid dates, and synonyms. Use this when you already have a concept_id and need its details.. It is categorised as a Read tool in the Omophub MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_concept? +

Register the Omophub 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 Omophub. Nothing to install.

What risk level is get_concept? +

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

Can I rate-limit get_concept? +

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.

How do I block get_concept completely? +

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.

What MCP server provides get_concept? +

get_concept is provided by the Omophub MCP server (@omophub/omophub-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Omophub tool call.

Deterministic rules across all 11 Omophub tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.