get_compound_record

What get_compound_record does on OrigeneMCP

AI agents call get_compound_record to retrieve information from OrigeneMCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_compound_record is rated Low

The verb 'Retrieve' and context of 'record object list' are consistent with a Read operation that queries biomedical compound data. No side effects, modifications, deletions, or executions are described. Severity is low because retrieval of compound records poses minimal risk even if accessed by an AI agent without authorization—it returns informational data only.

From the tool's definition Tool name 'get_compound_record' and description 'Retrieve compound record object list' indicate a data retrieval operation with no modification capability.

The rule that runs get_compound_record safely

PolicyLayer is an MCP gateway: it sits between your AI agents and OrigeneMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_compound_record, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_compound_record": {}
  }
}

Questions about get_compound_record