Fetch PubMed sources (IDs/URLs) for a given inhibitor compound.
AI agents call get_inhibitor_sources to retrieve information from Aurora-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing bibliographic metadata (PubMed IDs and URLs) related to inhibitor compounds. It performs a structured search and retrieval operation without modifying, executing, or destructively affecting any data. The operation is informational in nature and carries minimal risk if misused by an AI agent—it simply returns public reference data.
From the tool's definition Tool description: 'Fetch PubMed sources (IDs/URLs) for a given inhibitor compound.' The verb 'Fetch' indicates data retrieval. The function retrieves bibliographic references and URLs from PubMed, which are read-only operations with no side effects on data.
Attacks that exploit this kind of access
Fetch PubMed sources (IDs/URLs) for a given inhibitor compound. It is categorised as a Read tool in the Aurora-MCP MCP Server, which means it retrieves data without modifying state.
Register the Aurora- MCP server in PolicyLayer and add a rule for get_inhibitor_sources: 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 Aurora-MCP. Nothing to install.
get_inhibitor_sources 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_inhibitor_sources 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_inhibitor_sources. 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_inhibitor_sources is provided by the Aurora- MCP server (ndaniel/aurora-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 →