Low Risk

find_entity_id

find_entity_id

How to control find_entity_id ↓

What find_entity_id does on PubTator-MCP-Server

AI agents call find_entity_id to retrieve information from PubTator-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 find_entity_id needs a policy

The tool appears to be a lookup utility for retrieving entity identifiers in a biomedical literature annotation system. This is a read-only operation with no side effects. Confidence is moderate (0.72) because the description is empty; if it unexpectedly performed identifier generation or modification, the category could change, but the context strongly suggests a simple query function.

From the tool's definition Tool name 'find_entity_id' suggests looking up or retrieving an identifier from a biomedical knowledge base. Sibling tools include 'search_pubtator' and 'find_related_entities', which are clearly Read operations.

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

How to control find_entity_id

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

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

find_entity_id 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 PubTator-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 find_entity_id

What does the find_entity_id tool do? +

find_entity_id. It is categorised as a Read tool in the PubTator-MCP-Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_entity_id? +

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

What risk level is find_entity_id? +

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

Can I rate-limit find_entity_id? +

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

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

find_entity_id is provided by the PubTator-MCP-Server MCP server (jackkuo666/pubtator-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 PubTator-MCP-Server tool call.

Start from PubTator-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.

5 PubTator-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.