Low Risk

get_summary

Resolve PubMed IDs (from search_pubmed) to citation metadata: title, authors, journal, publication date, DOI. Batch up to ~200 IDs per call as a comma-separated string — much cheaper than calling per-ID. Use when you have PMIDs and need the citation; for the abstract text use get_abstract instead.

Part of the Puumed server.

get_summary 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 PUUMED →

Free to start. No card required.

AI agents call get_summary to retrieve information from Puumed 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_summary 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_summary": {}
  }
}

See the full Puumed policy for all 23 tools.

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

ENFORCE ON MY PUUMED →

View all 23 tools →

These attack patterns abuse exactly the kind of access get_summary 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_summary only ever does what you allow.

SECURE PUUMED →

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

What does the get_summary tool do? +

Resolve PubMed IDs (from search_pubmed) to citation metadata: title, authors, journal, publication date, DOI. Batch up to ~200 IDs per call as a comma-separated string — much cheaper than calling per-ID. Use when you have PMIDs and need the citation; for the abstract text use get_abstract instead.. It is categorised as a Read tool in the Puumed MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_summary? +

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

What risk level is get_summary? +

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

Can I rate-limit get_summary? +

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

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

get_summary is provided by the Puumed MCP server (https://gateway.pipeworx.io/pubmed/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Puumed tool call.

Deterministic rules across all 23 Puumed 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.