Low Risk

diagnose_institutional_access

diagnose_institutional_access

How to control diagnose_institutional_access ↓

What diagnose_institutional_access does on Pubmed Search

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

Low Risk

Why diagnose_institutional_access needs a policy

The tool name indicates diagnosis/checking of institutional access permissions, which is a read-only operation that retrieves status information without modifying or executing anything. While the empty description reduces confidence, the operational context (research assistant for literature search) and naming pattern suggest this queries access availability rather than modifying it.

From the tool's definition Tool name 'diagnose_institutional_access' suggests querying or checking access status. No description provided, limiting certainty.

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

How to control diagnose_institutional_access

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

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

diagnose_institutional_access 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 Pubmed Search — 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 diagnose_institutional_access

What does the diagnose_institutional_access tool do? +

diagnose_institutional_access. It is categorised as a Read tool in the Pubmed Search MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on diagnose_institutional_access? +

Register the Pubmed Search MCP server in PolicyLayer and add a rule for diagnose_institutional_access: 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 Pubmed Search. Nothing to install.

What risk level is diagnose_institutional_access? +

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

Can I rate-limit diagnose_institutional_access? +

Yes. Add a rate_limit block to the diagnose_institutional_access 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 diagnose_institutional_access completely? +

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

diagnose_institutional_access is provided by the Pubmed Search MCP server (u9401066/pubmed-search-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pubmed Search tool call.

Start from Pubmed Search, 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.

63 Pubmed Search 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.