Low Risk

resolve_identifier_to_sources

Resolve a DOI/PMID/PMCID to candidate source URLs with provenance and confidence metadata.

How to control resolve_identifier_to_sources ↓

What resolve_identifier_to_sources does on MedSci Agent

AI agents call resolve_identifier_to_sources to retrieve information from MedSci Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why resolve_identifier_to_sources needs a policy

This tool resolves bibliographic identifiers to URLs — a pure lookup/query operation with no side effects. It retrieves metadata and candidate URLs without creating, modifying, or deleting any data.

From the tool's definition Resolve a DOI/PMID/PMCID to candidate source URLs with provenance and confidence metadata

Documented attack patterns abuse exactly the kind of access resolve_identifier_to_sources gives an agent:

How to control resolve_identifier_to_sources

PolicyLayer is an MCP gateway — it sits between your AI agents and MedSci Agent, and nothing reaches the server without passing your rules. This is the rule we recommend for resolve_identifier_to_sources:

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

resolve_identifier_to_sources is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MedSci Agent — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about resolve_identifier_to_sources

What does the resolve_identifier_to_sources tool do? +

Resolve a DOI/PMID/PMCID to candidate source URLs with provenance and confidence metadata. It is categorised as a Read tool in the MedSci Agent MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on resolve_identifier_to_sources? +

Register the MedSci Agent MCP server in PolicyLayer and add a rule for resolve_identifier_to_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 MedSci Agent. Nothing to install.

What risk level is resolve_identifier_to_sources? +

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

Can I rate-limit resolve_identifier_to_sources? +

Yes. Add a rate_limit block to the resolve_identifier_to_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.

How do I block resolve_identifier_to_sources completely? +

Set action: deny in the PolicyLayer policy for resolve_identifier_to_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.

What MCP server provides resolve_identifier_to_sources? +

resolve_identifier_to_sources is provided by the MedSci Agent MCP server (omar-a-hassan/medsci-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MedSci Agent tool call.

Start from MedSci Agent, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

28 MedSci Agent tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.