Low Risk

get_detailed_metrics

Get detailed performance metrics for the specified time period (default: last 24 hours).

How to control get_detailed_metrics ↓

What get_detailed_metrics does on NCBI Literature Search MCP Server

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

Low Risk

Why get_detailed_metrics needs a policy

This tool retrieves and queries performance metrics data without creating, modifying, deleting, or executing operations. It is purely informational and read-only, consistent with the Read category for tools that retrieve data without side effects.

From the tool's definition Tool name 'get_detailed_metrics' and description 'Get detailed performance metrics for the specified time period' indicate retrieval of existing performance data with no modification or side effects.

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

How to control get_detailed_metrics

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

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

get_detailed_metrics 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 NCBI Literature Search MCP Server — 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 get_detailed_metrics

What does the get_detailed_metrics tool do? +

Get detailed performance metrics for the specified time period (default: last 24 hours). It is categorised as a Read tool in the NCBI Literature Search MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_detailed_metrics? +

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

What risk level is get_detailed_metrics? +

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

Can I rate-limit get_detailed_metrics? +

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

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

get_detailed_metrics is provided by the NCBI Literature Search MCP Server MCP server (vitorpavinato/ncbi-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every NCBI Literature Search MCP Server tool call.

Start from NCBI Literature Search MCP Server, 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.

12 NCBI Literature Search MCP Server 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.